0s autopkgtest [16:57:58]: starting date: 2024-03-08 0s autopkgtest [16:57:58]: git checkout: d9c0295 adt_testbed.py: supress warnings from apt using a shell pipeline 0s autopkgtest [16:57:58]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.rf1z8km0/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --setup-commands /home/ubuntu/autopkgtest/setup-commands/setup-testbed --apt-pocket=proposed=src:pygobject,src:glib2.0 --apt-upgrade libfprint --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=pygobject/3.47.0-3build1 glib2.0/2.79.3-3ubuntu1' -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-2@bos01-arm64-14.secgroup --name adt-noble-arm64-libfprint-20240308-165758-juju-7f2275-prod-proposed-migration-environment-2 --image adt/ubuntu-noble-arm64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-2 --net-id=net_prod-proposed-migration -e TERM=linux -e ''"'"'http_proxy=http://squid.internal:3128'"'"'' -e ''"'"'https_proxy=http://squid.internal:3128'"'"'' -e ''"'"'no_proxy=127.0.0.1,127.0.1.1,login.ubuntu.com,localhost,localdomain,novalocal,internal,archive.ubuntu.com,ports.ubuntu.com,security.ubuntu.com,ddebs.ubuntu.com,changelogs.ubuntu.com,launchpadlibrarian.net,launchpadcontent.net,launchpad.net,10.24.0.0/24,keystone.ps5.canonical.com,objectstorage.prodstack5.canonical.com'"'"'' --mirror=http://us.ports.ubuntu.com/ubuntu-ports/ 113s autopkgtest [16:59:51]: @@@@@@@@@@@@@@@@@@@@ test bed setup 114s Get:1 http://ftpmaster.internal/ubuntu noble-proposed InRelease [117 kB] 114s Get:2 http://ftpmaster.internal/ubuntu noble-proposed/main Sources [439 kB] 114s Get:3 http://ftpmaster.internal/ubuntu noble-proposed/restricted Sources [3976 B] 114s Get:4 http://ftpmaster.internal/ubuntu noble-proposed/universe Sources [2584 kB] 115s Get:5 http://ftpmaster.internal/ubuntu noble-proposed/multiverse Sources [35.7 kB] 115s Get:6 http://ftpmaster.internal/ubuntu noble-proposed/main arm64 Packages [580 kB] 115s Get:7 http://ftpmaster.internal/ubuntu noble-proposed/main arm64 c-n-f Metadata [3144 B] 115s Get:8 http://ftpmaster.internal/ubuntu noble-proposed/restricted arm64 Packages [20.3 kB] 115s Get:9 http://ftpmaster.internal/ubuntu noble-proposed/restricted arm64 c-n-f Metadata [116 B] 115s Get:10 http://ftpmaster.internal/ubuntu noble-proposed/universe arm64 Packages [2803 kB] 115s Get:11 http://ftpmaster.internal/ubuntu noble-proposed/universe arm64 c-n-f Metadata [8528 B] 115s Get:12 http://ftpmaster.internal/ubuntu noble-proposed/multiverse arm64 Packages [38.2 kB] 115s Get:13 http://ftpmaster.internal/ubuntu noble-proposed/multiverse arm64 c-n-f Metadata [116 B] 117s Fetched 6632 kB in 1s (4746 kB/s) 117s Reading package lists... 121s Reading package lists... 121s Building dependency tree... 121s Reading state information... 121s Calculating upgrade... 122s The following packages will be REMOVED: 122s libglib2.0-0 122s The following NEW packages will be installed: 122s libglib2.0-0t64 xdg-user-dirs 122s The following packages will be upgraded: 122s gir1.2-glib-2.0 libglib2.0-data python3-gi shim-signed 122s 4 upgraded, 2 newly installed, 1 to remove and 0 not upgraded. 122s Need to get 2562 kB of archives. 122s After this operation, 264 kB disk space will be freed. 122s Get:1 http://ftpmaster.internal/ubuntu noble-proposed/main arm64 gir1.2-glib-2.0 arm64 2.79.3-3ubuntu3 [182 kB] 122s Get:2 http://ftpmaster.internal/ubuntu noble-proposed/main arm64 python3-gi arm64 3.47.0-3build1 [233 kB] 122s Get:3 http://ftpmaster.internal/ubuntu noble-proposed/main arm64 libglib2.0-0t64 arm64 2.79.3-3ubuntu3 [1527 kB] 122s Get:4 http://ftpmaster.internal/ubuntu noble-proposed/main arm64 libglib2.0-data all 2.79.3-3ubuntu3 [46.6 kB] 122s Get:5 http://ftpmaster.internal/ubuntu noble/main arm64 xdg-user-dirs arm64 0.18-1 [18.1 kB] 122s Get:6 http://ftpmaster.internal/ubuntu noble/main arm64 shim-signed arm64 1.57+15.8-0ubuntu1 [555 kB] 123s Preconfiguring packages ... 123s Fetched 2562 kB in 1s (4105 kB/s) 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 ... 75862 files and directories currently installed.) 123s Preparing to unpack .../gir1.2-glib-2.0_2.79.3-3ubuntu3_arm64.deb ... 123s Unpacking gir1.2-glib-2.0:arm64 (2.79.3-3ubuntu3) over (2.79.2-1~ubuntu1) ... 123s Preparing to unpack .../python3-gi_3.47.0-3build1_arm64.deb ... 123s Unpacking python3-gi (3.47.0-3build1) over (3.47.0-3) ... 123s dpkg: libglib2.0-0:arm64: dependency problems, but removing anyway as you requested: 123s udisks2 depends on libglib2.0-0 (>= 2.77.0). 123s shared-mime-info depends on libglib2.0-0 (>= 2.75.3). 123s python3-dbus depends on libglib2.0-0 (>= 2.16.0). 123s netplan.io depends on libglib2.0-0 (>= 2.70.0). 123s netplan-generator depends on libglib2.0-0 (>= 2.70.0). 123s libxmlb2:arm64 depends on libglib2.0-0 (>= 2.54.0). 123s libvolume-key1:arm64 depends on libglib2.0-0 (>= 2.18.0). 123s libudisks2-0:arm64 depends on libglib2.0-0 (>= 2.75.3). 123s libqrtr-glib0:arm64 depends on libglib2.0-0 (>= 2.56). 123s libqmi-proxy depends on libglib2.0-0 (>= 2.30.0). 123s libqmi-glib5:arm64 depends on libglib2.0-0 (>= 2.54.0). 123s libpolkit-gobject-1-0:arm64 depends on libglib2.0-0 (>= 2.38.0). 123s libpolkit-agent-1-0:arm64 depends on libglib2.0-0 (>= 2.38.0). 123s libnetplan0:arm64 depends on libglib2.0-0 (>= 2.75.3). 123s libmm-glib0:arm64 depends on libglib2.0-0 (>= 2.62.0). 123s libmbim-proxy depends on libglib2.0-0 (>= 2.56). 123s libmbim-glib4:arm64 depends on libglib2.0-0 (>= 2.56). 123s libjson-glib-1.0-0:arm64 depends on libglib2.0-0 (>= 2.75.3). 123s libjcat1:arm64 depends on libglib2.0-0 (>= 2.75.3). 123s libgusb2:arm64 depends on libglib2.0-0 (>= 2.75.3). 123s libgudev-1.0-0:arm64 depends on libglib2.0-0 (>= 2.38.0). 123s libgirepository-1.0-1:arm64 depends on libglib2.0-0 (>= 2.79.0). 123s libfwupd2:arm64 depends on libglib2.0-0 (>= 2.79.0). 123s libblockdev3:arm64 depends on libglib2.0-0 (>= 2.42.2). 123s libblockdev-utils3:arm64 depends on libglib2.0-0 (>= 2.75.3). 123s libblockdev-swap3:arm64 depends on libglib2.0-0 (>= 2.42.2). 123s libblockdev-part3:arm64 depends on libglib2.0-0 (>= 2.42.2). 123s libblockdev-nvme3:arm64 depends on libglib2.0-0 (>= 2.42.2). 123s libblockdev-mdraid3:arm64 depends on libglib2.0-0 (>= 2.42.2). 123s libblockdev-loop3:arm64 depends on libglib2.0-0 (>= 2.42.2). 123s libblockdev-fs3:arm64 depends on libglib2.0-0 (>= 2.42.2). 123s libblockdev-crypto3:arm64 depends on libglib2.0-0 (>= 2.42.2). 123s fwupd depends on libglib2.0-0 (>= 2.79.0). 123s bolt depends on libglib2.0-0 (>= 2.56.0). 123s 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 ... 75861 files and directories currently installed.) 123s Removing libglib2.0-0:arm64 (2.79.2-1~ubuntu1) ... 123s Selecting previously unselected package libglib2.0-0t64:arm64. 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 ... 75836 files and directories currently installed.) 123s Preparing to unpack .../libglib2.0-0t64_2.79.3-3ubuntu3_arm64.deb ... 123s libglib2.0-0t64.preinst: Removing /var/lib/dpkg/info/libglib2.0-0:arm64.postrm to avoid loss of /usr/share/glib-2.0/schemas/gschemas.compiled... 123s removed '/var/lib/dpkg/info/libglib2.0-0:arm64.postrm' 123s Unpacking libglib2.0-0t64:arm64 (2.79.3-3ubuntu3) ... 123s Preparing to unpack .../libglib2.0-data_2.79.3-3ubuntu3_all.deb ... 123s Unpacking libglib2.0-data (2.79.3-3ubuntu3) over (2.79.2-1~ubuntu1) ... 123s Selecting previously unselected package xdg-user-dirs. 123s Preparing to unpack .../xdg-user-dirs_0.18-1_arm64.deb ... 123s Unpacking xdg-user-dirs (0.18-1) ... 123s Preparing to unpack .../shim-signed_1.57+15.8-0ubuntu1_arm64.deb ... 123s Unpacking shim-signed (1.57+15.8-0ubuntu1) over (1.56+15.7-0ubuntu1) ... 123s Setting up xdg-user-dirs (0.18-1) ... 123s Setting up shim-signed (1.57+15.8-0ubuntu1) ... 124s Installing grub to /boot/efi. 124s Installing for arm64-efi platform. 124s Installation finished. No error reported. 124s Setting up libglib2.0-0t64:arm64 (2.79.3-3ubuntu3) ... 124s No schema files found: doing nothing. 124s Setting up libglib2.0-data (2.79.3-3ubuntu3) ... 124s Setting up gir1.2-glib-2.0:arm64 (2.79.3-3ubuntu3) ... 124s Setting up python3-gi (3.47.0-3build1) ... 124s Processing triggers for man-db (2.12.0-3) ... 124s Processing triggers for libc-bin (2.39-0ubuntu2) ... 125s W: Target Packages (main/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target CNF (main/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target Packages (universe/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target Packages (universe/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target CNF (universe/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target CNF (universe/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target Packages (restricted/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target Packages (restricted/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target CNF (restricted/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target CNF (restricted/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target Packages (multiverse/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target Packages (multiverse/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target CNF (multiverse/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target CNF (multiverse/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target Packages (main/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target CNF (main/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target Packages (universe/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target Packages (universe/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target CNF (universe/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target CNF (universe/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target Packages (restricted/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target Packages (restricted/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target CNF (restricted/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target CNF (restricted/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target Packages (multiverse/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target Packages (multiverse/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target CNF (multiverse/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target CNF (multiverse/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 125s W: Target Packages (main/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 125s W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 125s W: Target CNF (main/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 125s W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 125s W: Target Packages (universe/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 125s W: Target Packages (universe/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 125s W: Target CNF (universe/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 125s W: Target CNF (universe/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 125s W: Target Packages (restricted/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 125s W: Target Packages (restricted/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 125s W: Target CNF (restricted/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 125s W: Target CNF (restricted/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 125s W: Target Packages (multiverse/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 125s W: Target Packages (multiverse/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 125s W: Target CNF (multiverse/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 125s W: Target CNF (multiverse/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 125s Reading package lists... 125s Building dependency tree... 125s Reading state information... 125s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 126s sh: Attempting to set up Debian/Ubuntu apt sources automatically 126s sh: Distribution appears to be Ubuntu 129s Reading package lists... 129s Building dependency tree... 129s Reading state information... 129s eatmydata is already the newest version (131-1). 129s dbus is already the newest version (1.14.10-4ubuntu1). 129s dbus set to manually installed. 129s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 129s W: Target Packages (main/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target CNF (main/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1Reading package lists... 129s W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target Packages (universe/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target Packages (universe/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target CNF (universe/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target CNF (universe/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target Packages (restricted/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target Packages (restricted/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target CNF (restricted/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target CNF (restricted/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target Packages (multiverse/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target Packages (multiverse/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target CNF (multiverse/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target CNF (multiverse/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target Packages (main/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target CNF (main/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target Packages (universe/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target Packages (universe/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target CNF (universe/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target CNF (universe/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target Packages (restricted/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target Packages (restricted/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target CNF (restricted/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target CNF (restricted/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target Packages (multiverse/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target Packages (multiverse/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target CNF (multiverse/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target CNF (multiverse/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 129s W: Target Packages (main/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 129s W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 129s W: Target CNF (main/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 129s W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 129s W: Target Packages (universe/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 129s W: Target Packages (universe/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 129s W: Target CNF (universe/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 129s W: Target CNF (universe/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 129s W: Target Packages (restricted/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 129s W: Target Packages (restricted/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 129s W: Target CNF (restricted/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 129s W: Target CNF (restricted/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 129s W: Target Packages (multiverse/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 129s W: Target Packages (multiverse/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 129s W: Target CNF (multiverse/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 129s W: Target CNF (multiverse/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 129s 130s Building dependency tree... 130s Reading state information... 130s rng-tools-debian is already the newest version (2.4). 130s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 130s Reading package lists... 130s Building dependency tree... 130s Reading state information... 131s haveged is already the newest version (1.9.14-1ubuntu1). 131s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 131s Reading package lists... 131s Building dependency tree... 131s Reading state information... 131s The following packages will be REMOVED: 132s cloud-init* python3-configobj* python3-debconf* 132s 0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded. 132s After this operation, 3248 kB disk space will be freed. 132s (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 ... 75875 files and directories currently installed.) 132s Removing cloud-init (24.1-0ubuntu1) ... 132s Removing python3-configobj (5.0.8-3) ... 132s Removing python3-debconf (1.5.86) ... 132s Processing triggers for man-db (2.12.0-3) ... 133s (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 ... 75486 files and directories currently installed.) 133s Purging configuration files for cloud-init (24.1-0ubuntu1) ... 133s dpkg: warning: while removing cloud-init, directory '/etc/cloud/cloud.cfg.d' not empty so not removed 133s Processing triggers for rsyslog (8.2312.0-3ubuntu3) ... 134s Reading package lists... 134s Building dependency tree... 134s Reading state information... 134s linux-generic is already the newest version (6.8.0-11.11+1). 134s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 135s Hit:1 http://ftpmaster.internal/ubuntu noble InRelease 135s Hit:2 http://ftpmaster.internal/ubuntu noble-updates InRelease 135s Hit:3 http://ftpmaster.internal/ubuntu noble-security InRelease 135s Hit:4 http://ftpmaster.internal/ubuntu noble-proposed InRelease 135s Hit:5 http://ftpmaster.internal/ubuntu noble-backports InRelease 138s Reading package lists... 138s W: Target Packages (main/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (main/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (universe/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (universe/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (universe/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (universe/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (restricted/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (restricted/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (restricted/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (restricted/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (multiverse/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (multiverse/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (multiverse/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (multiverse/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (main/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Reading package lists...Target CNF (main/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (universe/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (universe/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (universe/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (universe/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (restricted/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (restricted/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (restricted/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (restricted/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (multiverse/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (multiverse/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (multiverse/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (multiverse/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (main/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target CNF (main/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target Packages (universe/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target Packages (universe/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target CNF (universe/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target CNF (universe/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target Packages (restricted/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target Packages (restricted/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target CNF (restricted/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target CNF (restricted/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target Packages (multiverse/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target Packages (multiverse/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target CNF (multiverse/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target CNF (multiverse/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target Packages (main/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (main/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (universe/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (universe/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (universe/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (universe/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (restricted/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (restricted/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (restricted/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (restricted/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (multiverse/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (multiverse/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (multiverse/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (multiverse/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (main/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (main/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (universe/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (universe/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (universe/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (universe/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (restricted/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (restricted/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (restricted/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (restricted/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (multiverse/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (multiverse/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (multiverse/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target CNF (multiverse/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 138s W: Target Packages (main/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target CNF (main/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target Packages (universe/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target Packages (universe/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target CNF (universe/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target CNF (universe/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target Packages (restricted/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target Packages (restricted/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target CNF (restricted/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target CNF (restricted/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target Packages (multiverse/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target Packages (multiverse/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target CNF (multiverse/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s W: Target CNF (multiverse/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 138s 138s Building dependency tree... 138s Reading state information... 139s Calculating upgrade... 139s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 139s Reading package lists... 139s Building dependency tree... 139s Reading state information... 140s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 140s autopkgtest [17:00:18]: rebooting testbed after setup commands that affected boot 175s autopkgtest [17:00:53]: testbed running kernel: Linux 6.8.0-11-generic #11-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 14 02:53:31 UTC 2024 176s autopkgtest [17:00:54]: testbed dpkg architecture: arm64 177s autopkgtest [17:00:55]: @@@@@@@@@@@@@@@@@@@@ apt-source libfprint 178s W: Target Packages (main/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target CNF (main/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target Packages (universe/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target Packages (universe/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target CNF (universe/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target CNF (universe/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target Packages (restricted/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target Packages (restricted/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target CNF (restricted/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target CNF (restricted/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target Packages (multiverse/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target Packages (multiverse/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target CNF (multiverse/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target CNF (multiverse/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:1 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target Packages (main/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target CNF (main/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target Packages (universe/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target Packages (universe/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target CNF (universe/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target CNF (universe/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target Packages (restricted/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target Packages (restricted/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target CNF (restricted/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target CNF (restricted/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target Packages (multiverse/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target Packages (multiverse/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target CNF (multiverse/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target CNF (multiverse/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:2 and /etc/apt/sources.list.d/ubuntu.sources:1 178s W: Target Packages (main/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 178s W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 178s W: Target CNF (main/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 178s W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 178s W: Target Packages (universe/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 178s W: Target Packages (universe/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 178s W: Target CNF (universe/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 178s W: Target CNF (universe/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 178s W: Target Packages (restricted/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 178s W: Target Packages (restricted/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 178s W: Target CNF (restricted/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 178s W: Target CNF (restricted/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 178s W: Target Packages (multiverse/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 178s W: Target Packages (multiverse/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 178s W: Target CNF (multiverse/cnf/Commands-arm64) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 178s W: Target CNF (multiverse/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list.d/ubuntu.sources:2 180s Get:1 http://ftpmaster.internal/ubuntu noble/main libfprint 1:1.94.7+tod1-0ubuntu1 (dsc) [2996 B] 180s Get:2 http://ftpmaster.internal/ubuntu noble/main libfprint 1:1.94.7+tod1-0ubuntu1 (tar) [9280 kB] 180s Get:3 http://ftpmaster.internal/ubuntu noble/main libfprint 1:1.94.7+tod1-0ubuntu1 (diff) [17.2 kB] 180s gpgv: Signature made Tue Feb 20 08:27:36 2024 UTC 180s gpgv: using RSA key D4C501DA48EB797A081750939449C2F50996635F 180s gpgv: Can't check signature: No public key 180s dpkg-source: warning: cannot verify inline signature for ./libfprint_1.94.7+tod1-0ubuntu1.dsc: no acceptable signature found 182s autopkgtest [17:01:00]: testing package libfprint version 1:1.94.7+tod1-0ubuntu1 182s autopkgtest [17:01:00]: build not needed 238s autopkgtest [17:01:56]: test installed-tests: preparing testbed 243s Reading package lists... 243s Building dependency tree... 243s Reading state information... 243s Correcting dependencies...Starting pkgProblemResolver with broken count: 0 243s Starting 2 pkgProblemResolver with broken count: 0 244s Done 244s Done 244s Starting pkgProblemResolver with broken count: 0 244s Starting 2 pkgProblemResolver with broken count: 0 244s Done 245s The following additional packages will be installed: 245s fontconfig-config fonts-dejavu-core fonts-dejavu-mono gir1.2-fprint-2.0 245s gir1.2-gusb-1.0 gir1.2-json-1.0 gnome-desktop-testing libcairo2 245s libfontconfig1 libfprint-2-2 libfprint-2-tests libfprint-2-tod1 245s libpixman-1-0 libumockdev0 libxcb-render0 libxcb-shm0 libxrender1 245s python3-cairo umockdev 245s The following NEW packages will be installed: 245s fontconfig-config fonts-dejavu-core fonts-dejavu-mono gir1.2-fprint-2.0 245s gir1.2-gusb-1.0 gir1.2-json-1.0 gnome-desktop-testing libcairo2 245s libfontconfig1 libfprint-2-2 libfprint-2-tests libfprint-2-tod1 245s libpixman-1-0 libumockdev0 libxcb-render0 libxcb-shm0 libxrender1 245s python3-cairo umockdev 245s 0 upgraded, 19 newly installed, 0 to remove and 0 not upgraded. 245s 1 not fully installed or removed. 245s Need to get 9522 kB of archives. 245s After this operation, 33.8 MB of additional disk space will be used. 245s Get:1 http://ftpmaster.internal/ubuntu noble/universe arm64 gnome-desktop-testing arm64 2021.1-3 [15.7 kB] 245s Get:2 http://ftpmaster.internal/ubuntu noble/main arm64 gir1.2-json-1.0 arm64 1.8.0-2 [8816 B] 245s Get:3 http://ftpmaster.internal/ubuntu noble/main arm64 gir1.2-gusb-1.0 arm64 0.4.8-1 [7454 B] 245s Get:4 http://ftpmaster.internal/ubuntu noble/main arm64 libpixman-1-0 arm64 0.42.2-1 [193 kB] 245s Get:5 http://ftpmaster.internal/ubuntu noble/main arm64 libfprint-2-tod1 arm64 1:1.94.7+tod1-0ubuntu1 [62.3 kB] 245s Get:6 http://ftpmaster.internal/ubuntu noble/main arm64 libfprint-2-2 arm64 1:1.94.7+tod1-0ubuntu1 [262 kB] 245s Get:7 http://ftpmaster.internal/ubuntu noble/main arm64 gir1.2-fprint-2.0 arm64 1:1.94.7+tod1-0ubuntu1 [7220 B] 245s Get:8 http://ftpmaster.internal/ubuntu noble/main arm64 fonts-dejavu-mono all 2.37-8 [502 kB] 245s Get:9 http://ftpmaster.internal/ubuntu noble/main arm64 fonts-dejavu-core all 2.37-8 [835 kB] 245s Get:10 http://ftpmaster.internal/ubuntu noble/main arm64 fontconfig-config arm64 2.15.0-1ubuntu1 [37.0 kB] 245s Get:11 http://ftpmaster.internal/ubuntu noble/main arm64 libfontconfig1 arm64 2.15.0-1ubuntu1 [142 kB] 245s Get:12 http://ftpmaster.internal/ubuntu noble/main arm64 libxcb-render0 arm64 1.15-1 [16.1 kB] 245s Get:13 http://ftpmaster.internal/ubuntu noble/main arm64 libxcb-shm0 arm64 1.15-1 [5780 B] 245s Get:14 http://ftpmaster.internal/ubuntu noble/main arm64 libxrender1 arm64 1:0.9.10-1.1 [19.1 kB] 245s Get:15 http://ftpmaster.internal/ubuntu noble/main arm64 libcairo2 arm64 1.18.0-1 [550 kB] 245s Get:16 http://ftpmaster.internal/ubuntu noble/main arm64 python3-cairo arm64 1.25.1-2 [153 kB] 245s Get:17 http://ftpmaster.internal/ubuntu noble/universe arm64 libumockdev0 arm64 0.17.18-1 [70.4 kB] 245s Get:18 http://ftpmaster.internal/ubuntu noble/universe arm64 umockdev arm64 0.17.18-1 [71.8 kB] 245s Get:19 http://ftpmaster.internal/ubuntu noble/universe arm64 libfprint-2-tests arm64 1:1.94.7+tod1-0ubuntu1 [6563 kB] 246s Fetched 9522 kB in 1s (9383 kB/s) 246s Selecting previously unselected package gnome-desktop-testing. 246s (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 ... 75431 files and directories currently installed.) 246s Preparing to unpack .../00-gnome-desktop-testing_2021.1-3_arm64.deb ... 246s Unpacking gnome-desktop-testing (2021.1-3) ... 246s Selecting previously unselected package gir1.2-json-1.0:arm64. 246s Preparing to unpack .../01-gir1.2-json-1.0_1.8.0-2_arm64.deb ... 246s Unpacking gir1.2-json-1.0:arm64 (1.8.0-2) ... 246s Selecting previously unselected package gir1.2-gusb-1.0:arm64. 246s Preparing to unpack .../02-gir1.2-gusb-1.0_0.4.8-1_arm64.deb ... 246s Unpacking gir1.2-gusb-1.0:arm64 (0.4.8-1) ... 246s Selecting previously unselected package libpixman-1-0:arm64. 246s Preparing to unpack .../03-libpixman-1-0_0.42.2-1_arm64.deb ... 246s Unpacking libpixman-1-0:arm64 (0.42.2-1) ... 246s Selecting previously unselected package libfprint-2-tod1:arm64. 246s Preparing to unpack .../04-libfprint-2-tod1_1%3a1.94.7+tod1-0ubuntu1_arm64.deb ... 246s Unpacking libfprint-2-tod1:arm64 (1:1.94.7+tod1-0ubuntu1) ... 246s Selecting previously unselected package libfprint-2-2. 246s Preparing to unpack .../05-libfprint-2-2_1%3a1.94.7+tod1-0ubuntu1_arm64.deb ... 246s Unpacking libfprint-2-2 (1:1.94.7+tod1-0ubuntu1) ... 246s Selecting previously unselected package gir1.2-fprint-2.0:arm64. 246s Preparing to unpack .../06-gir1.2-fprint-2.0_1%3a1.94.7+tod1-0ubuntu1_arm64.deb ... 246s Unpacking gir1.2-fprint-2.0:arm64 (1:1.94.7+tod1-0ubuntu1) ... 246s Selecting previously unselected package fonts-dejavu-mono. 246s Preparing to unpack .../07-fonts-dejavu-mono_2.37-8_all.deb ... 246s Unpacking fonts-dejavu-mono (2.37-8) ... 246s Selecting previously unselected package fonts-dejavu-core. 246s Preparing to unpack .../08-fonts-dejavu-core_2.37-8_all.deb ... 246s Unpacking fonts-dejavu-core (2.37-8) ... 246s Selecting previously unselected package fontconfig-config. 246s Preparing to unpack .../09-fontconfig-config_2.15.0-1ubuntu1_arm64.deb ... 246s Unpacking fontconfig-config (2.15.0-1ubuntu1) ... 246s Selecting previously unselected package libfontconfig1:arm64. 246s Preparing to unpack .../10-libfontconfig1_2.15.0-1ubuntu1_arm64.deb ... 246s Unpacking libfontconfig1:arm64 (2.15.0-1ubuntu1) ... 246s Selecting previously unselected package libxcb-render0:arm64. 246s Preparing to unpack .../11-libxcb-render0_1.15-1_arm64.deb ... 246s Unpacking libxcb-render0:arm64 (1.15-1) ... 246s Selecting previously unselected package libxcb-shm0:arm64. 246s Preparing to unpack .../12-libxcb-shm0_1.15-1_arm64.deb ... 246s Unpacking libxcb-shm0:arm64 (1.15-1) ... 246s Selecting previously unselected package libxrender1:arm64. 246s Preparing to unpack .../13-libxrender1_1%3a0.9.10-1.1_arm64.deb ... 246s Unpacking libxrender1:arm64 (1:0.9.10-1.1) ... 246s Selecting previously unselected package libcairo2:arm64. 246s Preparing to unpack .../14-libcairo2_1.18.0-1_arm64.deb ... 246s Unpacking libcairo2:arm64 (1.18.0-1) ... 246s Selecting previously unselected package python3-cairo. 246s Preparing to unpack .../15-python3-cairo_1.25.1-2_arm64.deb ... 246s Unpacking python3-cairo (1.25.1-2) ... 247s Selecting previously unselected package libumockdev0:arm64. 247s Preparing to unpack .../16-libumockdev0_0.17.18-1_arm64.deb ... 247s Unpacking libumockdev0:arm64 (0.17.18-1) ... 247s Selecting previously unselected package umockdev. 247s Preparing to unpack .../17-umockdev_0.17.18-1_arm64.deb ... 247s Unpacking umockdev (0.17.18-1) ... 247s Selecting previously unselected package libfprint-2-tests. 247s Preparing to unpack .../18-libfprint-2-tests_1%3a1.94.7+tod1-0ubuntu1_arm64.deb ... 247s Unpacking libfprint-2-tests (1:1.94.7+tod1-0ubuntu1) ... 247s Setting up gnome-desktop-testing (2021.1-3) ... 247s Setting up libpixman-1-0:arm64 (0.42.2-1) ... 247s Setting up libxrender1:arm64 (1:0.9.10-1.1) ... 247s Setting up libxcb-render0:arm64 (1.15-1) ... 247s Setting up libfprint-2-tod1:arm64 (1:1.94.7+tod1-0ubuntu1) ... 247s Setting up libxcb-shm0:arm64 (1.15-1) ... 247s Setting up fonts-dejavu-mono (2.37-8) ... 247s Setting up fonts-dejavu-core (2.37-8) ... 247s Setting up libumockdev0:arm64 (0.17.18-1) ... 247s Setting up gir1.2-json-1.0:arm64 (1.8.0-2) ... 247s Setting up libfprint-2-2 (1:1.94.7+tod1-0ubuntu1) ... 252s Setting up umockdev (0.17.18-1) ... 255s Setting up fontconfig-config (2.15.0-1ubuntu1) ... 255s Setting up gir1.2-gusb-1.0:arm64 (0.4.8-1) ... 255s Setting up libfontconfig1:arm64 (2.15.0-1ubuntu1) ... 255s Setting up gir1.2-fprint-2.0:arm64 (1:1.94.7+tod1-0ubuntu1) ... 255s Setting up libcairo2:arm64 (1.18.0-1) ... 255s Setting up python3-cairo (1.25.1-2) ... 255s Setting up libfprint-2-tests (1:1.94.7+tod1-0ubuntu1) ... 255s Setting up autopkgtest-satdep (0) ... 255s Processing triggers for man-db (2.12.0-3) ... 255s Processing triggers for udev (255.2-3ubuntu2) ... 255s Processing triggers for libc-bin (2.39-0ubuntu2) ... 256s (Reading database ... 75818 files and directories currently installed.) 256s Removing autopkgtest-satdep (0) ... 257s autopkgtest [17:02:15]: test installed-tests: gnome-desktop-testing-runner libfprint-2 257s autopkgtest [17:02:15]: test installed-tests: [----------------------- 257s Running test: libfprint-2/fp-device.test 257s TAP version 13 257s # random seed: R02Sa18c5e3234af7e2228f1ceabfe51405e 257s 1..17 257s # Start of device tests 257s # Start of async tests 257s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 257s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 257s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-MELGK2/virtual_image.socket 257s # libfprint-context-DEBUG: created 257s # libfprint-device-DEBUG: Device reported probe completion 257s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 257s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 257s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:15.394: 91379414: ../libfprint/drivers/virtual-image.c:216 257s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_device_connection-DEBUG: 17:02:15.394: 91379537: ../libfprint/drivers/virtual-device-listener.c:153 257s # libfprint-image_device-DEBUG: Image device open completed 257s # libfprint-device-DEBUG: Device reported open completion 257s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 257s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 257s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:15.495: 91480200: ../libfprint/drivers/virtual-image.c:244 257s # libfprint-image_device-DEBUG: Image device close completed 257s # libfprint-device-DEBUG: Device reported close completion 257s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 257s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 257s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 257s ok 1 /device/async/open 257s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 257s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 257s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 257s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-PM8YJ2/virtual_image.socket 257s # libfprint-context-DEBUG: created 257s # libfprint-device-DEBUG: Device reported probe completion 257s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 257s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 257s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:15.596: 91581624: ../libfprint/drivers/virtual-image.c:216 257s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_device_connection-DEBUG: 17:02:15.596: 91581641: ../libfprint/drivers/virtual-device-listener.c:153 257s # libfprint-image_device-DEBUG: Image device open completed 257s # libfprint-device-DEBUG: Device reported open completion 257s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 257s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 257s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:15.697: 91682153: ../libfprint/drivers/virtual-image.c:244 257s # libfprint-image_device-DEBUG: Image device close completed 257s # libfprint-device-DEBUG: Device reported close completion 257s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 257s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 257s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 257s ok 2 /device/async/close 257s # End of async tests 257s # Start of sync tests 257s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 257s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 257s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 257s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-BWB6J2/virtual_image.socket 257s # libfprint-context-DEBUG: created 257s # libfprint-device-DEBUG: Device reported probe completion 257s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 257s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 257s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:15.799: 91784048: ../libfprint/drivers/virtual-image.c:216 257s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_device_connection-DEBUG: 17:02:15.799: 91784110: ../libfprint/drivers/virtual-device-listener.c:153 257s # libfprint-image_device-DEBUG: Image device open completed 257s # libfprint-device-DEBUG: Device reported open completion 257s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 257s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 257s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:15.899: 91884491: ../libfprint/drivers/virtual-image.c:244 258s # libfprint-image_device-DEBUG: Image device close completed 258s # libfprint-device-DEBUG: Device reported close completion 258s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 258s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 258s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 258s ok 3 /device/sync/open 258s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 258s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 258s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 258s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-Y4QBK2/virtual_image.socket 258s # libfprint-context-DEBUG: created 258s # libfprint-device-DEBUG: Device reported probe completion 258s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 258s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 258s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:16.001: 91985902: ../libfprint/drivers/virtual-image.c:216 258s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_device_connection-DEBUG: 17:02:16.001: 91985918: ../libfprint/drivers/virtual-device-listener.c:153 258s # libfprint-image_device-DEBUG: Image device open completed 258s # libfprint-device-DEBUG: Device reported open completion 258s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 258s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 258s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:16.101: 92086468: ../libfprint/drivers/virtual-image.c:244 258s # libfprint-image_device-DEBUG: Image device close completed 258s # libfprint-device-DEBUG: Device reported close completion 258s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 258s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 258s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 258s ok 4 /device/sync/close 258s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 258s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 258s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 258s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-WYL7J2/virtual_image.socket 258s # libfprint-context-DEBUG: created 258s # libfprint-device-DEBUG: Device reported probe completion 258s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 258s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 258s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:16.203: 92188299: ../libfprint/drivers/virtual-image.c:216 258s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_device_connection-DEBUG: 17:02:16.203: 92188360: ../libfprint/drivers/virtual-device-listener.c:153 258s # libfprint-image_device-DEBUG: Image device open completed 258s # libfprint-device-DEBUG: Device reported open completion 258s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 258s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 258s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:16.304: 92288909: ../libfprint/drivers/virtual-image.c:244 258s # libfprint-image_device-DEBUG: Image device close completed 258s # libfprint-device-DEBUG: Device reported close completion 258s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 258s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 258s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 258s ok 5 /device/sync/get_driver 258s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 258s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 258s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 258s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-E9QEK2/virtual_image.socket 258s # libfprint-context-DEBUG: created 258s # libfprint-device-DEBUG: Device reported probe completion 258s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 258s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 258s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:16.405: 92390115: ../libfprint/drivers/virtual-image.c:216 258s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_device_connection-DEBUG: 17:02:16.405: 92390131: ../libfprint/drivers/virtual-device-listener.c:153 258s # libfprint-image_device-DEBUG: Image device open completed 258s # libfprint-device-DEBUG: Device reported open completion 258s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 258s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 258s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:16.505: 92490666: ../libfprint/drivers/virtual-image.c:244 258s # libfprint-image_device-DEBUG: Image device close completed 258s # libfprint-device-DEBUG: Device reported close completion 258s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 258s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 258s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 258s ok 6 /device/sync/get_device_id 258s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 258s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 258s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 258s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-2ERYJ2/virtual_image.socket 258s # libfprint-context-DEBUG: created 258s # libfprint-device-DEBUG: Device reported probe completion 258s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 258s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 258s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:16.607: 92592295: ../libfprint/drivers/virtual-image.c:216 258s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_device_connection-DEBUG: 17:02:16.607: 92592357: ../libfprint/drivers/virtual-device-listener.c:153 258s # libfprint-image_device-DEBUG: Image device open completed 258s # libfprint-device-DEBUG: Device reported open completion 258s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 258s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 258s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:16.708: 92692964: ../libfprint/drivers/virtual-image.c:244 258s # libfprint-image_device-DEBUG: Image device close completed 258s # libfprint-device-DEBUG: Device reported close completion 258s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 258s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 258s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 258s ok 7 /device/sync/get_name 258s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 258s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 258s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 258s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-DYU5J2/virtual_image.socket 258s # libfprint-context-DEBUG: created 258s # libfprint-device-DEBUG: Device reported probe completion 258s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 258s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 258s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:16.809: 92794779: ../libfprint/drivers/virtual-image.c:216 258s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_device_connection-DEBUG: 17:02:16.809: 92794839: ../libfprint/drivers/virtual-device-listener.c:153 259s # libfprint-image_device-DEBUG: Image device open completed 259s # libfprint-device-DEBUG: Device reported open completion 259s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 259s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 259s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:16.910: 92895430: ../libfprint/drivers/virtual-image.c:244 259s # libfprint-image_device-DEBUG: Image device close completed 259s # libfprint-device-DEBUG: Device reported close completion 259s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 259s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 259s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 259s ok 8 /device/sync/get_scan_type 259s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 259s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 259s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 259s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-UDZBK2/virtual_image.socket 259s # libfprint-context-DEBUG: created 259s # libfprint-device-DEBUG: Device reported probe completion 259s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 259s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 259s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:17.011: 92996740: ../libfprint/drivers/virtual-image.c:216 259s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_device_connection-DEBUG: 17:02:17.011: 92996756: ../libfprint/drivers/virtual-device-listener.c:153 259s # libfprint-image_device-DEBUG: Image device open completed 259s # libfprint-device-DEBUG: Device reported open completion 259s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 259s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 259s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:17.112: 93097256: ../libfprint/drivers/virtual-image.c:244 259s # libfprint-image_device-DEBUG: Image device close completed 259s # libfprint-device-DEBUG: Device reported close completion 259s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 259s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 259s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 259s ok 9 /device/sync/get_finger_status 259s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 259s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 259s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 259s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-N1T7J2/virtual_image.socket 259s # libfprint-context-DEBUG: created 259s # libfprint-device-DEBUG: Device reported probe completion 259s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 259s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 259s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:17.213: 93198471: ../libfprint/drivers/virtual-image.c:216 259s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_device_connection-DEBUG: 17:02:17.213: 93198486: ../libfprint/drivers/virtual-device-listener.c:153 259s # libfprint-image_device-DEBUG: Image device open completed 259s # libfprint-device-DEBUG: Device reported open completion 259s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 259s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 259s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:17.314: 93298978: ../libfprint/drivers/virtual-image.c:244 259s # libfprint-image_device-DEBUG: Image device close completed 259s # libfprint-device-DEBUG: Device reported close completion 259s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 259s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 259s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 259s ok 10 /device/sync/get_nr_enroll_stages 259s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 259s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 259s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 259s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-F6AEK2/virtual_image.socket 259s # libfprint-context-DEBUG: created 259s # libfprint-device-DEBUG: Device reported probe completion 259s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 259s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 259s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:17.415: 93400245: ../libfprint/drivers/virtual-image.c:216 259s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_device_connection-DEBUG: 17:02:17.415: 93400261: ../libfprint/drivers/virtual-device-listener.c:153 259s # libfprint-image_device-DEBUG: Image device open completed 259s # libfprint-device-DEBUG: Device reported open completion 259s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 259s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 259s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:17.515: 93500808: ../libfprint/drivers/virtual-image.c:244 259s # libfprint-image_device-DEBUG: Image device close completed 259s # libfprint-device-DEBUG: Device reported close completion 259s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 259s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 259s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 259s ok 11 /device/sync/supports_identify 259s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 259s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 259s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 259s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-U1YYJ2/virtual_image.socket 259s # libfprint-context-DEBUG: created 259s # libfprint-device-DEBUG: Device reported probe completion 259s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 259s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 259s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:17.617: 93602217: ../libfprint/drivers/virtual-image.c:216 259s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_device_connection-DEBUG: 17:02:17.617: 93602232: ../libfprint/drivers/virtual-device-listener.c:153 259s # libfprint-image_device-DEBUG: Image device open completed 259s # libfprint-device-DEBUG: Device reported open completion 259s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 259s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 259s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:17.717: 93702733: ../libfprint/drivers/virtual-image.c:244 259s # libfprint-image_device-DEBUG: Image device close completed 259s # libfprint-device-DEBUG: Device reported close completion 259s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 259s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 259s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 259s ok 12 /device/sync/supports_capture 259s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 259s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 259s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 259s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-HE25J2/virtual_image.socket 259s # libfprint-context-DEBUG: created 259s # libfprint-device-DEBUG: Device reported probe completion 259s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 259s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 259s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:17.819: 93804288: ../libfprint/drivers/virtual-image.c:216 259s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_device_connection-DEBUG: 17:02:17.819: 93804304: ../libfprint/drivers/virtual-device-listener.c:153 259s # libfprint-image_device-DEBUG: Image device open completed 259s # libfprint-device-DEBUG: Device reported open completion 259s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 259s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 259s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:17.919: 93904649: ../libfprint/drivers/virtual-image.c:244 260s # libfprint-image_device-DEBUG: Image device close completed 260s # libfprint-device-DEBUG: Device reported close completion 260s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 260s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 260s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 260s ok 13 /device/sync/has_storage 260s # Start of open tests 260s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 260s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 260s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 260s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-1MFBK2/virtual_image.socket 260s # libfprint-context-DEBUG: created 260s # libfprint-device-DEBUG: Device reported probe completion 260s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 260s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 260s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:18.021: 94005964: ../libfprint/drivers/virtual-image.c:216 260s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_device_connection-DEBUG: 17:02:18.021: 94005980: ../libfprint/drivers/virtual-device-listener.c:153 260s # libfprint-image_device-DEBUG: Image device open completed 260s # libfprint-device-DEBUG: Device reported open completion 260s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 260s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 260s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:18.121: 94106482: ../libfprint/drivers/virtual-image.c:244 260s # libfprint-image_device-DEBUG: Image device close completed 260s # libfprint-device-DEBUG: Device reported close completion 260s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 260s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 260s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 260s ok 14 /device/sync/open/notify 260s # End of open tests 260s # Start of close tests 260s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 260s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 260s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 260s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-GHD7J2/virtual_image.socket 260s # libfprint-context-DEBUG: created 260s # libfprint-device-DEBUG: Device reported probe completion 260s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 260s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 260s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:18.222: 94207786: ../libfprint/drivers/virtual-image.c:216 260s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_device_connection-DEBUG: 17:02:18.222: 94207803: ../libfprint/drivers/virtual-device-listener.c:153 260s # libfprint-image_device-DEBUG: Image device open completed 260s # libfprint-device-DEBUG: Device reported open completion 260s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 260s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 260s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:18.323: 94308380: ../libfprint/drivers/virtual-image.c:244 260s # libfprint-image_device-DEBUG: Image device close completed 260s # libfprint-device-DEBUG: Device reported close completion 260s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 260s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 260s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 260s ok 15 /device/sync/close/notify 260s # End of close tests 260s # Start of identify tests 260s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 260s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 260s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 260s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-FFIEK2/virtual_image.socket 260s # libfprint-context-DEBUG: created 260s # libfprint-device-DEBUG: Device reported probe completion 260s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 260s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 260s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:18.424: 94409633: ../libfprint/drivers/virtual-image.c:216 260s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_device_connection-DEBUG: 17:02:18.424: 94409649: ../libfprint/drivers/virtual-device-listener.c:153 260s # libfprint-image_device-DEBUG: Image device open completed 260s # libfprint-device-DEBUG: Device reported open completion 260s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 260s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 260s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:18.525: 94510160: ../libfprint/drivers/virtual-image.c:244 260s # libfprint-image_device-DEBUG: Image device close completed 260s # libfprint-device-DEBUG: Device reported close completion 260s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 260s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 260s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 260s ok 16 /device/sync/identify/cancelled 260s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 260s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 260s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 260s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-S4TZJ2/virtual_image.socket 260s # libfprint-context-DEBUG: created 260s # libfprint-device-DEBUG: Device reported probe completion 260s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 260s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 260s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:18.626: 94611497: ../libfprint/drivers/virtual-image.c:216 260s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_device_connection-DEBUG: 17:02:18.626: 94611514: ../libfprint/drivers/virtual-device-listener.c:153 260s # libfprint-image_device-DEBUG: Image device open completed 260s # libfprint-device-DEBUG: Device reported open completion 260s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 260s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 260s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:1948): libfprint-virtual_image-DEBUG: 17:02:18.727: 94712089: ../libfprint/drivers/virtual-image.c:244 260s # libfprint-image_device-DEBUG: Image device close completed 260s # libfprint-device-DEBUG: Device reported close completion 260s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 260s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 260s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 260s ok 17 /device/sync/identify/null-prints 260s # End of identify tests 260s # End of sync tests 260s # End of device tests 260s PASS: libfprint-2/fp-device.test 260s Running test: libfprint-2/driver-vfs7552.test 260s ** (umockdev-run:1988): DEBUG: 17:02:18.887: umockdev.vala:123: Created udev test bed /tmp/umockdev.R8G5J2 260s ** (umockdev-run:1988): DEBUG: 17:02:18.891: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-7 260s ** (umockdev-run:1988): DEBUG: 17:02:18.892: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-7 (subsystem usb) 260s ** (umockdev-run:1988): DEBUG: 17:02:18.894: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.R8G5J2/dev/bus/usb/001/003 260s ** (umockdev-run:1988): DEBUG: 17:02:18.894: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 260s ** (umockdev-run:1988): DEBUG: 17:02:18.895: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 260s ** (umockdev-run:1988): DEBUG: 17:02:18.897: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.R8G5J2/dev/bus/usb/001/001 260s ** (umockdev-run:1988): DEBUG: 17:02:18.897: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 260s ** (umockdev-run:1988): DEBUG: 17:02:18.897: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 260s (umockdev-run:1988): GLib-GIO-DEBUG: 17:02:18.899: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 261s (process:1992): libfprint-context-DEBUG: 17:02:18.980: Initializing FpContext (libfprint version 1.94.7+tod1) 261s (process:1992): libfprint-tod-DEBUG: 17:02:18.981: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 261s (process:1992): libfprint-context-DEBUG: 17:02:18.982: No driver found for USB device 1D6B:0002 261s (process:1992): libfprint-device-DEBUG: 17:02:18.983: Device reported probe completion 261s (process:1992): libfprint-device-DEBUG: 17:02:18.983: Completing action FPI_DEVICE_ACTION_PROBE in idle! 261s (process:1992): libfprint-device-DEBUG: 17:02:18.983: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s libusb: error [op_handle_events] cannot find handle for fd 9 261s (process:1992): libfprint-SSM-DEBUG: 17:02:18.986: [vfs7552] DEV_OPEN_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:18.986: [vfs7552] DEVICE OPEN entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:18.986: Sending vfs7552_cmd_01 261s (process:1992): libfprint-SSM-DEBUG: 17:02:18.987: [vfs7552] DEVICE OPEN entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:18.987: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:18.987: Got 38 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:18.987: [vfs7552] DEVICE OPEN entering state 2 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:18.987: Sending vfs7552_cmd_19 261s (process:1992): libfprint-SSM-DEBUG: 17:02:18.987: [vfs7552] DEVICE OPEN entering state 3 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:18.987: Receiving 128 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:18.988: Got 68 bytes out of 128 261s (process:1992): libfprint-SSM-DEBUG: 17:02:18.988: [vfs7552] DEVICE OPEN entering state 4 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:18.988: Sending vfs7552_init_00 261s (process:1992): libfprint-SSM-DEBUG: 17:02:18.988: [vfs7552] DEVICE OPEN entering state 5 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:18.988: Receiving 64 bytes 261s (process:1992): libfprint-SSM-DEBUG: 17:02:18.989: [vfs7552] DEVICE OPEN entering state 6 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:18.989: Sending vfs7552_init_01 261s (process:1992): libfprint-SSM-DEBUG: 17:02:18.989: [vfs7552] DEVICE OPEN entering state 7 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:18.989: Receiving 64 bytes 261s (process:1992): libfprint-SSM-DEBUG: 17:02:18.989: [vfs7552] DEVICE OPEN entering state 8 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:18.989: Sending vfs7552_init_02 261s (process:1992): libfprint-SSM-DEBUG: 17:02:18.990: [vfs7552] DEVICE OPEN entering state 9 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:18.990: Receiving 64 bytes 261s (process:1992): libfprint-SSM-DEBUG: 17:02:18.990: [vfs7552] DEVICE OPEN entering state 10 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:18.990: Sending vfs7552_init_03 261s (process:1992): libfprint-SSM-DEBUG: 17:02:18.991: [vfs7552] DEVICE OPEN entering state 11 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:18.991: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:18.991: Got 10 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:18.991: [vfs7552] DEVICE OPEN entering state 12 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:18.991: Sending vfs7552_init_04 261s (process:1992): libfprint-SSM-DEBUG: 17:02:18.992: [vfs7552] DEVICE OPEN entering state 13 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:18.992: Receiving 64 bytes 261s (process:1992): libfprint-SSM-DEBUG: 17:02:18.992: [vfs7552] DEVICE OPEN completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:18.992: [vfs7552] DEV_OPEN_NUM_STATES completed successfully 261s (process:1992): libfprint-image_device-DEBUG: 17:02:18.992: Image device open completed 261s (process:1992): libfprint-device-DEBUG: 17:02:18.992: Device reported open completion 261s (process:1992): libfprint-device-DEBUG: 17:02:18.992: Completing action FPI_DEVICE_ACTION_OPEN in idle! 261s (process:1992): libfprint-device-DEBUG: 17:02:18.992: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 261s (process:1992): libfprint-device-DEBUG: 17:02:18.992: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 261s (process:1992): libfprint-image_device-DEBUG: 17:02:18.992: Activating image device 261s (process:1992): libfprint-image_device-DEBUG: 17:02:18.992: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 261s (process:1992): libfprint-image_device-DEBUG: 17:02:18.992: Image device activation completed 261s (process:1992): libfprint-image_device-DEBUG: 17:02:18.992: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 261s (process:1992): libfprint-image_device-DEBUG: 17:02:18.992: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 261s (process:1992): libfprint-device-DEBUG: 17:02:18.992: Device reported finger status change: FP_FINGER_STATUS_NEEDED 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.043: changing to 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.043: [vfs7552] ACTIVATE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.043: [vfs7552] ACTIVATE INIT entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.043: Sending vfs7552_image_start 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.043: [vfs7552] ACTIVATE INIT entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.043: Receiving 2048 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.044: Got 1962 bytes out of 2048 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.044: [vfs7552] ACTIVATE INIT completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.044: [vfs7552] ACTIVATE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.044: [vfs7552] ACTIVATE INTERRUPT QUERY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.044: Receiving 8 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.044: Got 5 bytes out of 8 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.044: [vfs7552] ACTIVATE INTERRUPT QUERY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.044: [vfs7552] ACTIVATE_NUM_STATES entering state 2 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.044: [vfs7552] ACTIVATE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.044: [vfs7552] ACTIVATE INTERRUPT QUERY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.044: Receiving 8 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.045: Got 5 bytes out of 8 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.045: [vfs7552] ACTIVATE INTERRUPT QUERY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.045: [vfs7552] ACTIVATE_NUM_STATES entering state 2 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.045: [vfs7552] ACTIVATE_NUM_STATES entering state 3 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.045: [vfs7552] ACTIVATE_NUM_STATES completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.045: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.045: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.045: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.045: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.045: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.046: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.046: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.046: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.046: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.046: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.046: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.046: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.046: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.046: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.046: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.046: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.046: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.046: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.046: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.047: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.047: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.047: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.047: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.047: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.047: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.047: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.047: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.048: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.048: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.048: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.048: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.048: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.048: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.048: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.048: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.049: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.049: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.049: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.049: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.049: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.049: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.049: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.049: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.050: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.050: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.050: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.050: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.050: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.050: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.050: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.050: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.051: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.051: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.051: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.051: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.051: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.051: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.051: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.051: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.052: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.052: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.052: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.052: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.052: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.052: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.052: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.052: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.053: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.053: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.053: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.053: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.053: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.053: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.053: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.053: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.054: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.054: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.054: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.054: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.054: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.054: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.054: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.054: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.054: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.055: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.055: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.055: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.055: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.055: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.055: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.055: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.055: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.055: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.056: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.056: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.056: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.056: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.056: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.056: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.056: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.056: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.057: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.057: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.057: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.057: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.057: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.057: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.057: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.057: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.058: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.058: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.058: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.058: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.058: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.058: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.058: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.058: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.058: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.058: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.058: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.058: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.058: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.058: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.059: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.059: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.059: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.059: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.059: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.059: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.059: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.059: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.060: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.060: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.060: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.060: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.060: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.060: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.060: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.060: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.061: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.061: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.061: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.061: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.061: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.061: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.061: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.061: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.062: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.062: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.062: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.062: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.062: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.062: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.062: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.062: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.062: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.062: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.063: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.063: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.063: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.063: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.063: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.063: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.063: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.063: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.064: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.064: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.064: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.064: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.064: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.064: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.064: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.064: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.065: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.065: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.065: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.065: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.065: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.065: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.065: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.065: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.065: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.065: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.065: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.065: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.065: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.065: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.066: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.066: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.066: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.066: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.066: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.066: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.067: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.067: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.067: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.067: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.067: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.067: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.067: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.067: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.068: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.068: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.068: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.068: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.068: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.068: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.068: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.068: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.069: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.069: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.069: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.069: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.069: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.069: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.069: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.069: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.069: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.069: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.070: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.070: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.070: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.070: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.070: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.070: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.070: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.070: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.071: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.071: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.071: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.071: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.071: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.071: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.071: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.071: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.071: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.071: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.071: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.071: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.071: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.071: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.072: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.072: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.072: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.072: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.072: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.072: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.072: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.072: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.073: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.073: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.073: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.073: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.073: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.073: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.073: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.073: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.074: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.074: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.074: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.074: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.074: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.074: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.074: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.074: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.075: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.075: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.075: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.075: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.075: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.075: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.075: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.075: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.075: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.075: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.076: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.076: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.076: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.076: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.076: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.076: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.076: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.076: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.077: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.077: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.077: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.077: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.077: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.077: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.077: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.077: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.078: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.078: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.078: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.078: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.078: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.078: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.078: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.078: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.078: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.078: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.078: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.078: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.078: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.078: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.079: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.079: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.079: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.079: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.079: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.079: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.079: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.079: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.080: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.080: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.080: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.080: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.080: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.080: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.080: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.080: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.081: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.081: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.081: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.081: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.081: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.081: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.081: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.081: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.082: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.082: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.082: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.082: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.082: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.082: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.082: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.082: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.082: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.083: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.083: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.083: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.083: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.083: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.083: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.083: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.083: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.083: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.084: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.084: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.084: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.084: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.084: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.084: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.084: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.084: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.085: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.085: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.085: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.085: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.085: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.085: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.085: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.085: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.086: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.086: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.086: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.086: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.086: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.086: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.086: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.086: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.086: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.086: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.086: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.086: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.086: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.086: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.087: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.087: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.087: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.087: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.087: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.087: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.087: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.087: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.088: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.088: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.088: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.088: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.088: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.088: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.088: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.088: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.089: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.089: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.089: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.089: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.089: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.089: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.089: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.089: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.090: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.090: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.090: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.090: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.090: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.090: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.090: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.090: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.090: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.090: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.091: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.091: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.091: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.091: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.091: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.091: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.091: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.091: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.092: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.092: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.092: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.092: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.092: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.092: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.092: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.092: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.093: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.093: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.093: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.093: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.093: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.093: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.093: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.093: Receiving 64 bytes 261s (process:1992): libfprint-device-DEBUG: 17:02:19.093: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.094: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.094: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.094: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.094: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.094: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.094: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.094: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.094: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.094: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.094: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.095: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.095: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.096: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.096: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.096: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.096: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.096: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.096: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.096: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.096: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.096: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.096: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.096: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.096: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.096: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.096: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.097: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.097: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.097: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.097: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.097: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.097: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.097: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.097: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.098: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.098: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.098: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.098: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.098: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.098: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.098: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.098: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.099: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.099: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.099: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.099: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.099: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.099: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.099: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.099: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.099: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.099: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.100: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.100: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.100: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.100: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.100: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.100: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.100: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.100: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.101: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.101: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.101: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.101: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.101: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.101: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.101: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.101: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.102: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.102: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.102: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.102: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.102: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.102: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.102: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.102: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.102: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.102: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.102: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.102: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.102: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.102: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.103: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.103: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.103: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.103: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.103: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.103: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.103: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.103: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.104: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.104: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.104: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.104: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.104: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.104: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.104: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.104: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.105: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.105: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.105: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.105: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.105: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.105: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.105: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.105: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.105: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.105: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.106: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.106: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.106: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.106: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.106: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.106: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.106: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.106: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.107: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.107: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.107: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.107: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.107: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.107: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.107: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.107: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.108: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.108: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.108: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.108: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.108: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.108: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.108: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.108: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.108: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.108: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.108: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.108: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.108: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.108: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.109: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.109: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.109: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.109: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.109: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.109: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.109: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.109: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.110: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.110: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.110: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.110: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.110: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.110: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.110: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.110: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.111: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.111: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.111: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.111: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.111: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.111: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.111: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.111: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.112: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.112: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.112: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.112: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.112: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.112: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.112: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.112: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.112: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.112: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.113: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.113: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.113: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.113: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.113: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.113: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.113: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.113: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.114: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.114: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.114: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.114: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.114: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.114: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.114: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.114: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.115: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.115: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.115: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.115: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.115: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.115: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.115: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.115: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.115: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.115: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.115: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.115: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.115: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.115: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.116: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.116: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.116: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.116: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.116: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.116: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.116: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.116: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.117: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.117: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.117: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.117: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.117: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.117: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.117: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.117: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.118: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.118: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.118: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.118: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.118: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.118: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.118: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.118: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.119: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.119: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.119: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.119: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.119: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.119: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.119: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.119: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.120: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.120: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.120: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.120: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.120: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.120: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.120: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.120: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.121: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.121: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.121: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.121: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.121: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.121: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.121: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.121: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.121: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.121: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.122: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.122: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.122: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.122: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.122: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.122: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.122: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.122: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.123: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.123: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.123: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.123: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.123: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.123: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.123: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.123: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.124: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.124: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.124: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.124: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.124: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.124: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.124: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.124: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.125: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.125: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.125: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.125: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.125: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.125: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.125: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.125: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.125: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.125: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.125: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.125: [vfs7552] CAPTURE_NUM_STATES entering state 2 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.125: [vfs7552] REQUEST CHUNK entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.125: Sending vfs7552_read_image_chunk 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.126: [vfs7552] REQUEST CHUNK completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.126: [vfs7552] CAPTURE_NUM_STATES entering state 3 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.126: [vfs7552] CAPTURE_NUM_STATES entering state 2 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.126: [vfs7552] REQUEST CHUNK entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.126: Sending vfs7552_read_image_chunk 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.127: [vfs7552] REQUEST CHUNK completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.127: [vfs7552] CAPTURE_NUM_STATES entering state 3 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.127: [vfs7552] CAPTURE_NUM_STATES entering state 2 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.127: [vfs7552] REQUEST CHUNK entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.127: Sending vfs7552_read_image_chunk 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.127: [vfs7552] REQUEST CHUNK completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.127: [vfs7552] CAPTURE_NUM_STATES entering state 3 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.128: [vfs7552] CAPTURE_NUM_STATES entering state 4 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.128: variance_before = 396 261s 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.128: background stored 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.128: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.128: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.128: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.128: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.128: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.129: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.129: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.129: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.129: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.129: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.129: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.129: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.129: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.130: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.130: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.130: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.130: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.130: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.130: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.130: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.130: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.131: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.131: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.131: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.131: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.131: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.131: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.131: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.131: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.132: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.132: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.132: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.132: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.132: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.132: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.132: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.132: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.132: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.132: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.132: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.132: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.132: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.132: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.133: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.133: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.133: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.133: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.133: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.133: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.133: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.133: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.134: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.134: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.134: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.134: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.134: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.134: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.134: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.134: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.134: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.134: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.135: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.135: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.135: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.135: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.135: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.135: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.135: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.135: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.136: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.136: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.136: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.136: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.136: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.136: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.136: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.136: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.137: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.137: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.137: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.137: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.137: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.137: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.137: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.137: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.137: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.137: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.137: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.137: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.138: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.138: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.138: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.138: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.138: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.138: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.138: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.138: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.139: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.139: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.139: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.139: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.139: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.139: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.139: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.139: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.140: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.140: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.140: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.140: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.140: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.140: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.140: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.140: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.141: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.141: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.141: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.141: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.141: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.141: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.141: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.141: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.142: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.142: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.142: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.142: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.142: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.142: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.142: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.142: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.143: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.143: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.143: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.143: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.143: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.143: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.143: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.144: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.144: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.144: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.144: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.144: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.144: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.144: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.144: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.145: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.145: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.145: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.145: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.145: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.145: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.146: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.146: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.146: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.146: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.146: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.146: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.146: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.146: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.146: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.146: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.146: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.146: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.146: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.146: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.147: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.147: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.147: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.147: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.147: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.147: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.148: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.148: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.148: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.148: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.148: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.148: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.148: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.149: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.149: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.149: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.149: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.149: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.149: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.149: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.149: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.149: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.149: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.150: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.150: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.150: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.150: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.150: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.150: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.150: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.150: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.151: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.151: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.151: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.151: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.151: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.151: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.152: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.152: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.152: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.152: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.152: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.152: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.152: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.152: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.152: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.152: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.152: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.152: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.153: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.153: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.153: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.153: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.153: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.153: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.154: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.154: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.154: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.154: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.154: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.154: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.154: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.154: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.155: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.155: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.155: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.155: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.155: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.155: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.156: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.156: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.156: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.156: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.156: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.156: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.156: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.156: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.156: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.156: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.157: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.157: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.157: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.157: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.157: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.157: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.158: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.158: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.158: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.158: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.158: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.158: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.158: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.158: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.158: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.158: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.158: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.158: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.159: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.159: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.159: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.159: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.159: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.159: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.159: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.160: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.160: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.160: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.160: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.160: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.160: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.161: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.161: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.161: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.161: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.161: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.161: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.161: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.161: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.162: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.162: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.162: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.162: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.162: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.162: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.162: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.162: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.162: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.163: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.163: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.163: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.163: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.163: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.163: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.163: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.163: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.164: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.164: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.164: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.164: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.164: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.164: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.164: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.164: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.164: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.164: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.164: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.164: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.164: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.164: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.165: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.165: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.165: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.165: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.165: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.165: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.165: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.165: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.166: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.166: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.166: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.166: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.166: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.166: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.166: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.166: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.167: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.167: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.167: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.167: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.167: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.167: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.167: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.167: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.168: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.168: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.168: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.168: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.168: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.168: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.168: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.168: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.168: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.168: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.169: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.169: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.169: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.169: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.169: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.169: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.169: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.169: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.170: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.170: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.170: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.170: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.170: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.170: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.171: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.171: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.171: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.171: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.171: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.171: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.171: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.171: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.171: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.171: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.172: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.172: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.172: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.172: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.172: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.172: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.172: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.172: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.173: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.173: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.173: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.173: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.173: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.173: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.173: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.173: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.174: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.174: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.174: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.174: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.174: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.174: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.174: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.174: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.174: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.175: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.175: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.175: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.175: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.175: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.175: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.175: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.175: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.175: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.176: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.176: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.176: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.176: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.176: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.176: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.176: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.176: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.177: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.177: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.177: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.177: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.177: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.177: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.177: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.178: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.178: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.178: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.178: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.178: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.178: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.178: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.178: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.178: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.178: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.179: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.179: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.179: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.179: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.179: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.179: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.179: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.179: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.180: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.180: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.180: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.180: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.180: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.180: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.181: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.181: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.181: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.181: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.181: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.181: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.181: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.181: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.181: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.181: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.182: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.182: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.182: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.182: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.182: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.182: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.182: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.182: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.183: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.183: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.183: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.183: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.183: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.183: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.184: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.184: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.184: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.184: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.184: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.184: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.184: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.184: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.185: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.185: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.185: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.185: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.185: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.185: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.185: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.185: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.186: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.186: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.186: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.186: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.186: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.186: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.186: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.187: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.187: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.187: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.187: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.187: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.187: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.187: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.187: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.187: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.187: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.187: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.188: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.188: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.188: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.188: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.188: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.188: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.188: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.188: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.189: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.189: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.189: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.189: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.189: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.189: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.189: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.189: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.190: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.190: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.190: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.190: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.190: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.190: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.190: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.190: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.190: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.191: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.191: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.191: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.191: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.191: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.191: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.191: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.191: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.191: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.192: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.192: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.192: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.192: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.192: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.192: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.192: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.192: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.193: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.193: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.193: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.193: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.193: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.193: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.193: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.194: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.194: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.194: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.194: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.194: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.194: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.194: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.194: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.194: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.194: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.194: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.194: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.194: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.195: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.195: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.195: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.195: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.195: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.195: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.195: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.196: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.196: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.196: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.196: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.196: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.196: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.196: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.196: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.197: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.197: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.197: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.197: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.197: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.197: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.197: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.197: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.197: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.197: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.198: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.198: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.198: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.198: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.198: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.198: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.198: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.198: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.199: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.199: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.199: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.199: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.199: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.199: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.199: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.199: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.199: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.199: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.200: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.200: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.200: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.200: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.200: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.200: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.200: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.200: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.201: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.201: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.201: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.201: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.201: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.201: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.201: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.201: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.202: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.202: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.202: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.202: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.202: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.202: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.202: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.202: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.203: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.203: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.203: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.203: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.203: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.203: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.204: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.204: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.204: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.204: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.204: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.204: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.204: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.204: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.205: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.205: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.205: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.205: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.205: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.205: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.205: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.205: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.206: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.206: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.206: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.206: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.206: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.206: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.206: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.206: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.206: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.206: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.206: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.206: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.206: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.206: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.207: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.207: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.207: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.207: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.207: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.207: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.208: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.208: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.208: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.208: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.208: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.208: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.208: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.208: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.209: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.209: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.209: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.209: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.209: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.209: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.209: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.209: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.209: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.209: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.210: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.210: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.210: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.210: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.210: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.210: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.210: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.210: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.211: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.211: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.211: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.211: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.211: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.211: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.211: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.211: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.212: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.212: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.212: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.212: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.212: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.212: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.212: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.213: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.213: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.213: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.213: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.213: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.213: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.213: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.213: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.213: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.213: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.213: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.213: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.213: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.213: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.214: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.214: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.214: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.214: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.214: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.214: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.214: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.215: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.215: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.215: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.215: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.215: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.215: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.215: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.215: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.216: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.216: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.216: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.216: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.216: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.216: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.216: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.216: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.217: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.217: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.217: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.217: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.217: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.217: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.217: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.217: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.218: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.218: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.218: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.218: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.218: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.218: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.218: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.218: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.219: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.219: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.219: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.219: [vfs7552] CAPTURE_NUM_STATES entering state 2 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.219: [vfs7552] REQUEST CHUNK entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.219: Sending vfs7552_read_image_chunk 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.219: [vfs7552] REQUEST CHUNK completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.219: [vfs7552] CAPTURE_NUM_STATES entering state 3 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.220: [vfs7552] CAPTURE_NUM_STATES entering state 2 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.220: [vfs7552] REQUEST CHUNK entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.220: Sending vfs7552_read_image_chunk 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.220: [vfs7552] REQUEST CHUNK completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.220: [vfs7552] CAPTURE_NUM_STATES entering state 3 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.220: [vfs7552] CAPTURE_NUM_STATES entering state 2 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.220: [vfs7552] REQUEST CHUNK entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.220: Sending vfs7552_read_image_chunk 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.221: [vfs7552] REQUEST CHUNK completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.221: [vfs7552] CAPTURE_NUM_STATES entering state 3 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.221: [vfs7552] CAPTURE_NUM_STATES entering state 4 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.221: Cleaning image 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.221: variance_after = 20 261s 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.221: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.221: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.221: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.222: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.222: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.222: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.222: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.222: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.222: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.222: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.222: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.223: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.223: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.223: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.223: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.223: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.223: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.224: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.224: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.224: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.224: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.224: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.224: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.224: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.224: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.225: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.225: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.225: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.225: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.225: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.225: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.225: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.225: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.225: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.225: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.226: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.226: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.226: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.226: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.226: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.226: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.226: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.227: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.227: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.227: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.227: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.227: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.227: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.227: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.227: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.228: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.228: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.228: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.228: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.228: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.228: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.229: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.229: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.229: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.229: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.229: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.229: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.229: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.229: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.229: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.229: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.229: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.229: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.229: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.229: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.230: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.230: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.230: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.230: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.230: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.230: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.230: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.230: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.231: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.231: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.231: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.231: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.231: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.231: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.231: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.231: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.232: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.232: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.232: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.232: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.232: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.232: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.232: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.232: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.232: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.232: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.233: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.233: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.233: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.233: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.233: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.233: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.234: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.234: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.234: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.234: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.234: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.234: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.234: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.234: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.234: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.235: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.235: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.235: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.235: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.235: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.235: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.235: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.235: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.235: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.235: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.235: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.235: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.235: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.236: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.236: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.236: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.236: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.236: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.236: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.237: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.237: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.237: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.237: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.237: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.237: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.237: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.237: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.238: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.238: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.238: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.238: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.238: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.238: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.238: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.238: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.238: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.238: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.239: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.239: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.239: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.239: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.239: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.239: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.239: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.239: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.240: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.240: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.240: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.240: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.240: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.240: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.240: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.240: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.241: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.241: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.241: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.241: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.241: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.241: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.241: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.241: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.241: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.241: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.241: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.241: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.241: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.241: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.242: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.242: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.242: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.242: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.242: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.242: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.242: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.242: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.243: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.243: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.243: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.243: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.243: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.243: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.243: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.243: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.244: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.244: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.244: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.244: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.244: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.244: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.244: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.244: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.244: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.244: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.245: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.245: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.245: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.245: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.245: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.245: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.245: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.245: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.246: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.246: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.246: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.246: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.246: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.246: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.246: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.246: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.246: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.246: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.246: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.246: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.246: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.247: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.247: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.247: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.248: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.248: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.248: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.248: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.248: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.248: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.248: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.248: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.248: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.248: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.249: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.249: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.249: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.249: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.249: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.249: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.249: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.249: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.250: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.250: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.250: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.250: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.250: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.250: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.250: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.250: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.251: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.251: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.251: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.251: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.251: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.251: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.251: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.251: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.252: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.252: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.252: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.252: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.252: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.252: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.252: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.252: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.253: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.253: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.253: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.253: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.253: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.253: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.253: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.253: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.254: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.254: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.254: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.254: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.254: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.254: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.254: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.254: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.254: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.254: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.255: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.255: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.255: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.255: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.255: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.255: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.255: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.255: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.256: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.256: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.256: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.256: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.256: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.256: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.256: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.256: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.257: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.257: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.257: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.257: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.257: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.257: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.257: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.257: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.257: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.257: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.257: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.257: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.257: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.257: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.258: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.258: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.258: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.258: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.258: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.258: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.258: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.258: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.259: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.259: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.259: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.259: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.259: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.259: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.259: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.259: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.259: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.260: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.260: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.260: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.260: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.260: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.260: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.260: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.260: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.260: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.261: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.261: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.261: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.261: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.261: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.261: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.261: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.261: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.262: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.262: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.262: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.262: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.262: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.262: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.262: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.262: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.263: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.263: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.263: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.263: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.263: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.263: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.263: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.263: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.264: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.264: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.264: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.264: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.264: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.264: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.264: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.264: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.264: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.264: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.264: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.265: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.265: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.265: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.265: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.265: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.265: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.265: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.265: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.265: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.265: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.265: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.266: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.266: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.266: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.266: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.266: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.266: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.266: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.266: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.267: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.267: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.267: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.267: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.267: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.267: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.267: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.267: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.268: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.268: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.268: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.268: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.268: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.268: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.268: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.268: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.268: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.268: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.269: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.269: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.269: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.269: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.269: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.269: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.269: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.269: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.270: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.270: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.270: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.270: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.270: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.270: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.270: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.270: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.271: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.271: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.271: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.271: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.271: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.271: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.271: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.271: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.272: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.272: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.272: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.272: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.272: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.272: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.272: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.272: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.272: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.272: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.272: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.272: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.272: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.272: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.273: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.273: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.273: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.273: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.273: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.273: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.273: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.273: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.274: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.274: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.274: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.274: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.274: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.274: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.274: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.274: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.275: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.275: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.275: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.275: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.275: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.275: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.275: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.275: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.275: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.275: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.276: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.276: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.276: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.276: [vfs7552] CAPTURE_NUM_STATES entering state 2 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.276: [vfs7552] REQUEST CHUNK entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.276: Sending vfs7552_read_image_chunk 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.276: [vfs7552] REQUEST CHUNK completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.276: [vfs7552] CAPTURE_NUM_STATES entering state 3 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.277: [vfs7552] CAPTURE_NUM_STATES entering state 2 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.277: [vfs7552] REQUEST CHUNK entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.277: Sending vfs7552_read_image_chunk 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.277: [vfs7552] REQUEST CHUNK completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.277: [vfs7552] CAPTURE_NUM_STATES entering state 3 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.278: [vfs7552] CAPTURE_NUM_STATES entering state 2 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.278: [vfs7552] REQUEST CHUNK entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.278: Sending vfs7552_read_image_chunk 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.278: [vfs7552] REQUEST CHUNK completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.278: [vfs7552] CAPTURE_NUM_STATES entering state 3 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.278: [vfs7552] CAPTURE_NUM_STATES entering state 4 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.278: Cleaning image 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.278: variance_after = 18 261s 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.278: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.278: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.278: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.279: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.279: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.279: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.279: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.279: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.279: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.279: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.279: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.280: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.280: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.280: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.280: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.280: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.280: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.280: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.280: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.281: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.281: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.281: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.281: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.281: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.281: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.281: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.281: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.281: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.281: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.282: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.282: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.282: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.282: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.282: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.282: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.282: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.282: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.283: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.283: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.283: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.283: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.283: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.283: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.283: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.283: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.284: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.284: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.284: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.284: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.284: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.284: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.284: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.284: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.284: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.284: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.284: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.284: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.284: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.284: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.285: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.285: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.285: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.285: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.285: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.285: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.285: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.285: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.286: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.286: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.286: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.286: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.286: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.286: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.286: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.286: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.287: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.287: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.287: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.287: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.287: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.287: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.287: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.287: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.287: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.287: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.288: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.288: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.288: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.288: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.288: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.288: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.288: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.288: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.289: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.289: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.289: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.289: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.289: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.289: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.289: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.289: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.290: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.290: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.290: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.290: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.290: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.290: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.290: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.290: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.291: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.291: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.291: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.291: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.291: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.291: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.291: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.291: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.291: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.291: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.291: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.292: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.292: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.292: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.292: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.292: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.292: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.292: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.292: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.292: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.292: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.292: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.293: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.293: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.293: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.293: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.293: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.293: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.293: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.293: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.294: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.294: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.294: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.294: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.294: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.294: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.294: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.294: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.294: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.294: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.295: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.295: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.295: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.295: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.295: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.295: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.295: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.295: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.296: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.296: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.296: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.296: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.296: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.296: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.296: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.296: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.297: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.297: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.297: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.297: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.297: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.297: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.297: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.297: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.298: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.298: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.298: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.298: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.298: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.298: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.298: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.298: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.298: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.298: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.298: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.298: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.298: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.299: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.299: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.299: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.300: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.300: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.300: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.300: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.300: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.300: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.300: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.300: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.300: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.300: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.300: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.300: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.300: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.300: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.301: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.301: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.301: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.301: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.301: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.301: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.301: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.301: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.302: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.302: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.302: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.302: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.302: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.302: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.302: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.302: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.303: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.303: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.303: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.303: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.303: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.303: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.303: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.303: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.304: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.304: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.304: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.304: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.304: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.304: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.304: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.304: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.305: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.305: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.305: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.305: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.305: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.305: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.305: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.305: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.305: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.305: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.306: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.306: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.306: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.306: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.306: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.306: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.306: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.306: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.307: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.307: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.307: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.307: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.307: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.307: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.307: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.307: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.308: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.308: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.308: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.308: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.308: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.308: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.308: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.308: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.309: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.309: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.309: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.309: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.309: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.309: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.309: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.309: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.310: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.310: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.310: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.310: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.310: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.310: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.310: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.310: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.311: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.311: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.311: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.311: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.311: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.311: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.311: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.311: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.312: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.312: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.312: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.312: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.312: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.312: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.312: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.312: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.312: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.313: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.313: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.313: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.313: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.313: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.313: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.313: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.313: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.313: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.313: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.313: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.313: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.313: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.314: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.314: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.314: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.314: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.314: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.314: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.314: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.314: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.315: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.315: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.315: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.315: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.315: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.315: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.315: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.315: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.316: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.316: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.316: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.316: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.316: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.316: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.316: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.316: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.317: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.317: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.317: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.317: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.317: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.317: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.317: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.317: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.317: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.317: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.318: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.318: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.318: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.318: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.318: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.318: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.318: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.318: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.319: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.319: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.319: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.319: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.319: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.319: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.319: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.319: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.320: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.320: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.320: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.320: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.320: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.320: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.320: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.320: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.321: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.321: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.321: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.321: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.321: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.321: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.321: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.321: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.322: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.322: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.322: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.322: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.322: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.322: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.322: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.322: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.322: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.322: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.322: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.322: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.322: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.322: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.323: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.323: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.323: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.323: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.323: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.323: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.323: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.323: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.324: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.324: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.324: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.324: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.324: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.324: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.324: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.324: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.325: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.325: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.325: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.325: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.325: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.325: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.325: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.325: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.325: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.325: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.326: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.326: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.326: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.326: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.326: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.326: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.326: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.326: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.327: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.327: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.327: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.327: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.327: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.327: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.327: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.327: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.328: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.328: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.328: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.328: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.328: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.328: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.328: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.328: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.328: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.328: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.328: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.328: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.328: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.328: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.329: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.329: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.329: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.329: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.329: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.329: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.329: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.329: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.330: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.330: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.330: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.330: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.330: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.330: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.330: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.330: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.331: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.331: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.331: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.331: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.331: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.331: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.331: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.331: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.332: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.332: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.332: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.332: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.332: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.332: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.332: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.332: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.332: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.332: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.333: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.333: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.333: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.333: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.333: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.333: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.333: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.333: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.334: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.334: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.334: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.334: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.334: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.334: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.334: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.334: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.335: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.335: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.335: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.335: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.335: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.335: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.335: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.335: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.336: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.336: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.336: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.336: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.336: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.336: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.336: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.336: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.336: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.336: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.336: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.336: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.336: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.336: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.337: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.337: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.337: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.337: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.337: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.337: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.337: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.337: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.338: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.338: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.338: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.338: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.338: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.338: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.338: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.338: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.338: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.338: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.339: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.339: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.339: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.339: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.339: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.339: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.339: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.339: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.340: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.340: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.340: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.340: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.340: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.340: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.340: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.340: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.341: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.341: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.341: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.341: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.341: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.341: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.341: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.341: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.341: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.341: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.341: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.341: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.341: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.341: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.342: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.342: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.342: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.342: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.342: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.342: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.342: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.342: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.343: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.343: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.343: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.343: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.343: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.343: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.343: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.343: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.344: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.344: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.344: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.344: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.344: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.344: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.344: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.344: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.345: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.345: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.345: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.345: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.345: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.345: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.345: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.345: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.345: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.345: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.346: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.346: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.346: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.346: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.346: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.346: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.346: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.346: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.347: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.347: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.347: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.347: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.347: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.347: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.347: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.347: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.348: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.348: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.348: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.348: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.348: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.348: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.348: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.348: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.348: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.348: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.348: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.348: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.348: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.348: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.349: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.349: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.349: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.349: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.349: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.349: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.349: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.349: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.350: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.350: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.350: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.350: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.350: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.350: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.350: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.350: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.351: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.351: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.351: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.351: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.351: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.351: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.351: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.351: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.351: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.351: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.352: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.352: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.352: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.352: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.352: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.352: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.352: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.352: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.353: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.353: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.353: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.353: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.353: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.353: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.353: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.353: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.354: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.354: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.354: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.354: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.354: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.354: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.354: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.354: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.354: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.354: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.354: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.354: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.354: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.354: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.355: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.355: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.355: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.355: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.355: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.355: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.355: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.355: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.356: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.356: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.356: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.356: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.356: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.356: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.356: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.356: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.357: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.357: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.357: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.357: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.357: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.357: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.357: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.357: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.357: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.357: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.358: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.358: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.358: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.358: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.358: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.358: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.358: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.358: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.359: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.359: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.359: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.359: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.359: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.359: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.359: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.359: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.359: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.359: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.359: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.360: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.360: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.360: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.360: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.360: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.360: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.360: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.360: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.360: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.360: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.360: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.361: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.361: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.361: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.361: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.361: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.361: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.361: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.361: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.362: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.362: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.362: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.362: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.362: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.362: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.362: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.362: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.362: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.362: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.363: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.363: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.363: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.363: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.363: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.363: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.363: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.363: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.364: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.364: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.364: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.364: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.364: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.364: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.364: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.364: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.365: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.365: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.365: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.365: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.365: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.365: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.365: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.365: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.365: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.365: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.365: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.365: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.365: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.365: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.366: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.366: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.366: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.366: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.366: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.366: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.366: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.366: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.367: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.367: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.367: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.367: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.367: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.367: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.367: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.367: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.368: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.368: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.368: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.368: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.368: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.368: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.368: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.368: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.368: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.368: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.369: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.369: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.369: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.369: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.369: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.369: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.369: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.369: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.370: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.370: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.370: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.370: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.370: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.370: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.370: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.370: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.371: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.371: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.371: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.371: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.371: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.371: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.371: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.371: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.372: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.372: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.372: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.372: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.372: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.372: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.372: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.372: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.373: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.373: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.373: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.373: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.373: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.373: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.373: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.373: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.373: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.373: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.373: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.373: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.373: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.373: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.374: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.374: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.374: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.374: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.374: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.374: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.374: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.374: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.375: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.375: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.375: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.375: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.375: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.375: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.375: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.375: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.375: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.375: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.376: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.376: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.376: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.376: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.376: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.376: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.376: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.376: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.377: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.377: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.377: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.377: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.377: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.377: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.377: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.377: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.378: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.378: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.378: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.378: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.378: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.378: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.378: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.378: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.379: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.379: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.379: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.379: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.379: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.379: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.379: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.379: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.380: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.380: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.380: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.380: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.380: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.380: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.380: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.380: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.381: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.381: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.381: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.381: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.381: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.381: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.381: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.381: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.381: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.381: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.381: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.381: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.381: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.381: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.382: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.382: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.382: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.382: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.382: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.382: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.382: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.382: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.383: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.383: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.383: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.383: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.383: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.383: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.383: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.383: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.384: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.384: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.384: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.384: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.384: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.384: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.384: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.384: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.385: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.385: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.385: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.385: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.385: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.385: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.385: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.385: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.385: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.385: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.386: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.386: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.386: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.386: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.386: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.386: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.386: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.386: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.387: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.387: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.387: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.387: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.387: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.387: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.387: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.387: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.388: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.388: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.388: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.388: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.388: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.388: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.388: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.388: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.389: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.389: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.389: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.389: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.389: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.389: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.389: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.389: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.389: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.389: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.389: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.389: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.389: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.389: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.390: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.390: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.390: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.390: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.390: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.390: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.390: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.390: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.391: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.391: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.391: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.391: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.391: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.391: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.391: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.391: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.392: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.392: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.392: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.392: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.392: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.392: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.392: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.392: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.392: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.392: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.393: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.393: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.393: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.393: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.393: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.393: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.393: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.393: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.394: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.394: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.394: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.394: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.394: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.394: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.394: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.394: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.395: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.395: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.395: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.395: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.395: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.395: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.395: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.395: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.395: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.395: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.395: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.395: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.395: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.395: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.396: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.396: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.396: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.396: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.396: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.396: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.396: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.396: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.397: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.397: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.397: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.397: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.397: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.397: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.397: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.397: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.398: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.398: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.398: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.398: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.398: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.398: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.398: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.398: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.398: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.398: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.399: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.399: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.399: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.399: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.399: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.399: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.399: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.399: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.400: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.400: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.400: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.400: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.400: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.400: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.400: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.400: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.401: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.401: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.401: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.401: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.401: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.401: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.401: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.401: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.402: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.402: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.402: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.402: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.402: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.402: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.402: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.402: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.402: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.402: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.402: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.402: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.402: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.402: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.403: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.403: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.403: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.403: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.403: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.403: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.403: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.403: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.404: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.404: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.404: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.404: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.404: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.404: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.404: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.404: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.404: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.404: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.405: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.405: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.405: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.405: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.405: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.405: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.405: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.405: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.406: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.406: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.406: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.406: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.406: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.406: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.406: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.406: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.407: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.407: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.407: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.407: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.407: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.407: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.407: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.407: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.407: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.407: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.407: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.407: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.407: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.407: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.408: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.408: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.408: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.408: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.408: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.408: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.408: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.408: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.409: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.409: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.409: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.409: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.409: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.409: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.409: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.409: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.410: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.410: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.410: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.410: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.410: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.410: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.410: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.410: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.411: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.411: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.411: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.411: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.411: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.411: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.411: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.411: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.411: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.411: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.412: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.412: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.412: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.412: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.412: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.412: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.412: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.412: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.413: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.413: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.413: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.413: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.413: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.413: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.413: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.413: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.414: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.414: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.414: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.414: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.414: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.414: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.414: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.414: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.414: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.414: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.414: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.414: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.414: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.414: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.415: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.415: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.415: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.415: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.415: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.415: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.415: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.415: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.416: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.416: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.416: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.416: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.416: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.416: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.416: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.416: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.417: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.417: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.417: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.417: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.417: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.417: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.417: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.417: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.417: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.418: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.418: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.418: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.418: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.418: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.418: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.418: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.418: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.418: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.419: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.419: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.419: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.419: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.419: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.419: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.419: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.419: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.420: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.420: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.420: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.420: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.420: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.420: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.420: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.420: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.421: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.421: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.421: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.421: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.421: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.421: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.421: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.421: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.421: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.421: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.421: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.421: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.421: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.421: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.422: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.422: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.422: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.422: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.422: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.422: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.422: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.422: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.423: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.423: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.423: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.423: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.423: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.423: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.423: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.423: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.424: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.424: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.424: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.424: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.424: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.424: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.424: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.424: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.425: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.425: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.425: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.425: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.425: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.425: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.425: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.425: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.426: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.426: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.426: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.426: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.426: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.426: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.426: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.426: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.426: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.426: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.427: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.427: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.427: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.427: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.427: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.427: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.427: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.427: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.428: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.428: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.428: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.428: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.428: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.428: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.428: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.428: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.429: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.429: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.429: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.429: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.429: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.429: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.429: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.429: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.429: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.429: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.429: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.429: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.429: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.429: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.430: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.430: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.430: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.430: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.430: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.430: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.430: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.430: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.431: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.431: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.431: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.431: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.431: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.431: [vfs7552] CAPTURE_NUM_STATES entering state 2 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.431: [vfs7552] REQUEST CHUNK entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.431: Sending vfs7552_read_image_chunk 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.432: [vfs7552] REQUEST CHUNK completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.432: [vfs7552] CAPTURE_NUM_STATES entering state 3 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.432: [vfs7552] CAPTURE_NUM_STATES entering state 2 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.432: [vfs7552] REQUEST CHUNK entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.432: Sending vfs7552_read_image_chunk 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.432: [vfs7552] REQUEST CHUNK completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.432: [vfs7552] CAPTURE_NUM_STATES entering state 3 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.433: [vfs7552] CAPTURE_NUM_STATES entering state 2 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.433: [vfs7552] REQUEST CHUNK entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.433: Sending vfs7552_read_image_chunk 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.433: [vfs7552] REQUEST CHUNK completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.434: [vfs7552] CAPTURE_NUM_STATES entering state 3 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.434: [vfs7552] CAPTURE_NUM_STATES entering state 4 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.434: Cleaning image 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.434: variance_after = 20 261s 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.434: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.434: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.434: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.434: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.434: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.435: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.435: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.435: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.435: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.435: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.435: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.435: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.435: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.436: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.436: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.436: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.436: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.436: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.436: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.436: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.436: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.437: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.437: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.437: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.437: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.437: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.437: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.437: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.437: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.438: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.438: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.438: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.438: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.438: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.438: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.438: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.438: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.439: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.439: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.439: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.439: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.439: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.439: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.439: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.439: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.440: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.440: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.440: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.440: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.440: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.440: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.440: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.440: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.440: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.440: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.440: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.440: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.440: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.441: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.441: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.441: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.441: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.441: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.441: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.441: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.441: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.441: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.442: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.442: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.442: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.442: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.442: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.442: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.442: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.442: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.443: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.443: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.443: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.443: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.443: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.444: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.444: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.444: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.444: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.444: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.445: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.445: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.445: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.445: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.445: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.445: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.445: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.445: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.445: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.445: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.445: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.445: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.445: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.445: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.446: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.446: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.446: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.446: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.446: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.446: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.446: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.446: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.447: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.447: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.447: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.447: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.447: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.447: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.447: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.447: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.448: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.448: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.448: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.448: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.448: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.448: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.448: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.448: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.449: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.449: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.449: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.449: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.449: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.449: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.449: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.449: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.450: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.450: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.450: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.450: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.450: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.450: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.450: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.450: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.451: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.451: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.451: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.451: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.451: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.451: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.451: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.451: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.451: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.451: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.452: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.452: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.452: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.452: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.452: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.452: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.452: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.452: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.453: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.453: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.453: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.453: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.453: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.453: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.453: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.453: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.454: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.454: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.454: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.454: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.454: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.454: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.454: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.454: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.455: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.455: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.455: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.455: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.455: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.455: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.455: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.455: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.456: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.456: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.456: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.456: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.456: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.456: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.456: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.456: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.457: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.457: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.457: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.457: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.457: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.457: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.457: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.457: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.458: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.458: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.458: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.458: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.458: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.458: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.458: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.458: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.459: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.459: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.459: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.459: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.459: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.459: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.459: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.459: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.459: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.459: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.459: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.459: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.459: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.459: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.460: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.460: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.460: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.460: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.460: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.460: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.460: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.460: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.461: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.461: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.461: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.461: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.461: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.461: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.461: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.461: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.462: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.462: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.462: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.462: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.462: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.462: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.462: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.462: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.463: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.463: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.463: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.463: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.463: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.463: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.463: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.463: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.464: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.464: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.464: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.464: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.464: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.464: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.464: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.464: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.464: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.465: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.465: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.465: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.465: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.465: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.465: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.465: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.465: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.465: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.466: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.466: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.466: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.466: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.466: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.466: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.466: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.466: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.467: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.467: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.467: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.467: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.467: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.467: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.467: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.467: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.468: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.468: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.468: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.468: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.468: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.468: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.468: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.468: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.468: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.468: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.468: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.468: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.468: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.468: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.469: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.469: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.469: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.469: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.469: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.469: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.469: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.469: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.470: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.470: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.470: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.470: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.470: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.470: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.470: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.470: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.471: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.471: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.471: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.471: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.471: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.471: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.471: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.471: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.472: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.472: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.472: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.472: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.472: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.472: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.472: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.472: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.473: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.473: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.473: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.473: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.473: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.473: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.473: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.473: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.473: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.473: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.474: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.474: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.474: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.474: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.474: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.474: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.474: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.474: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.475: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.475: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.475: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.475: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.475: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.475: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.475: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.475: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.476: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.476: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.476: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.476: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.476: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.476: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.476: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.476: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.477: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.477: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.477: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.477: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.477: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.477: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.477: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.477: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.478: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.478: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.478: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.478: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.478: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.478: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.478: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.478: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.479: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.479: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.479: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.479: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.479: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.479: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.479: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.479: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.479: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.479: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.479: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.479: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.479: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.479: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.480: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.480: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.480: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.480: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.480: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.480: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.480: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.480: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.481: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.481: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.481: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.481: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.481: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.481: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.481: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.481: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.482: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.482: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.482: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.482: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.482: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.482: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.482: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.482: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.483: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.483: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.483: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.483: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.483: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.483: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.483: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.483: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.484: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.484: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.484: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.484: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.484: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.484: [vfs7552] CAPTURE_NUM_STATES entering state 2 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.484: [vfs7552] REQUEST CHUNK entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.484: Sending vfs7552_read_image_chunk 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.485: [vfs7552] REQUEST CHUNK completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.485: [vfs7552] CAPTURE_NUM_STATES entering state 3 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.485: [vfs7552] CAPTURE_NUM_STATES entering state 2 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.485: [vfs7552] REQUEST CHUNK entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.485: Sending vfs7552_read_image_chunk 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.485: [vfs7552] REQUEST CHUNK completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.485: [vfs7552] CAPTURE_NUM_STATES entering state 3 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.486: [vfs7552] CAPTURE_NUM_STATES entering state 2 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.486: [vfs7552] REQUEST CHUNK entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.486: Sending vfs7552_read_image_chunk 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.486: [vfs7552] REQUEST CHUNK completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.486: [vfs7552] CAPTURE_NUM_STATES entering state 3 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.487: [vfs7552] CAPTURE_NUM_STATES entering state 4 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.487: Cleaning image 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.487: variance_after = 18 261s 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.487: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.487: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.487: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.487: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.487: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.488: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.488: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.488: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.488: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.488: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.488: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.488: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.488: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.489: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.489: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.489: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.489: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.489: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.489: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.489: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.489: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.490: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.490: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.490: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.490: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.490: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.490: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.490: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.490: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.491: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.491: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.491: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.491: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.491: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.491: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.491: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.491: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.492: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.492: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.492: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.492: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.492: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.492: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.492: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.492: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.492: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.492: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.492: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.492: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.492: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.492: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.493: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.493: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.493: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.493: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.493: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.493: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.493: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.493: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.494: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.494: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.494: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.494: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.494: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.494: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.494: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.494: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.495: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.495: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.495: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.495: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.495: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.495: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.495: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.495: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.496: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.496: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.496: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.496: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.496: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.496: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.496: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.496: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.497: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.497: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.497: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.497: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.497: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.497: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.497: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.497: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.498: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.498: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.498: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.498: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.498: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.498: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.498: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.498: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.498: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.498: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.499: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.499: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.499: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.499: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.499: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.499: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.499: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.499: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.500: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.500: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.500: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.500: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.500: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.500: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.500: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.500: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.501: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.501: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.501: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.501: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.501: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.501: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.501: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.501: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.502: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.502: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.502: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.502: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.502: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.502: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.502: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.502: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.503: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.503: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.503: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.503: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.503: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.503: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.503: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.503: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.503: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.503: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.503: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.503: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.503: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.504: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.504: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.504: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.504: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.504: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.504: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.504: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.504: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.504: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.505: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.505: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.505: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.505: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.505: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.505: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.505: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.505: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.506: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.506: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.506: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.506: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.506: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.506: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.506: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.506: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.507: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.507: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.507: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.507: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.507: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.507: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.507: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.507: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.508: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.508: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.508: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.508: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.508: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.508: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.508: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.508: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.509: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.509: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.509: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.509: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.509: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.509: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.509: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.509: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.509: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.509: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.510: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.510: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.510: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.510: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.510: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.510: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.510: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.510: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.511: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.511: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.511: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.511: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.511: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.511: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.511: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.511: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.511: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.511: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.511: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.511: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.511: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.511: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.512: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.512: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.512: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.512: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.512: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.512: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.512: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.512: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.513: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.513: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.513: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.513: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.513: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.513: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.513: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.513: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.514: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.514: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.514: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.514: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.514: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.514: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.514: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.514: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.515: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.515: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.515: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.515: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.515: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.515: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.515: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.515: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.516: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.516: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.516: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.516: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.516: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.516: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.516: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.516: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.517: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.517: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.517: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.517: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.517: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.517: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.517: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.517: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.518: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.518: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.518: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.518: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.518: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.518: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.518: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.518: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.519: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.519: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.519: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.519: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.519: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.519: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.519: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.519: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.520: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.520: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.520: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.520: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.520: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.520: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.520: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.520: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.521: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.521: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.521: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.521: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.521: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.521: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.521: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.521: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.522: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.522: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.522: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.522: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.522: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.522: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.522: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.522: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.522: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.522: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.523: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.523: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.523: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.523: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.523: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.523: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.523: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.523: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.524: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.524: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.524: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.524: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.524: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.524: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.524: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.524: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.525: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.525: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.525: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.525: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.525: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.525: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.525: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.525: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.526: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.526: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.526: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.526: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.526: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.526: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.526: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.526: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.526: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.526: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.526: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.526: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.526: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.527: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.527: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.527: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.528: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.528: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.528: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.528: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.528: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.528: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.528: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.528: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.529: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.529: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.529: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.529: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.529: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.529: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.529: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.529: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.529: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.529: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.529: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.529: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.529: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.529: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.530: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.530: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.530: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.530: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.530: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.530: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.530: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.530: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.531: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.531: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.531: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.531: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.531: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.531: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.531: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.531: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.532: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.532: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.532: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.532: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.532: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.532: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.532: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.532: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.533: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.533: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.533: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.533: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.533: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.533: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.533: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.533: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.534: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.534: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.534: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.534: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.534: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.534: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.534: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.534: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.535: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.535: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.535: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.535: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.535: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.535: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.535: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.535: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.536: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.536: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.536: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.536: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.536: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.536: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.536: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.536: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.536: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.536: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.537: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.537: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.537: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.537: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.537: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.537: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.537: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.537: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.538: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.538: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.538: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.538: [vfs7552] CAPTURE_NUM_STATES entering state 2 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.538: [vfs7552] REQUEST CHUNK entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.538: Sending vfs7552_read_image_chunk 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.538: [vfs7552] REQUEST CHUNK completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.538: [vfs7552] CAPTURE_NUM_STATES entering state 3 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.539: [vfs7552] CAPTURE_NUM_STATES entering state 2 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.539: [vfs7552] REQUEST CHUNK entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.539: Sending vfs7552_read_image_chunk 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.539: [vfs7552] REQUEST CHUNK completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.539: [vfs7552] CAPTURE_NUM_STATES entering state 3 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.539: [vfs7552] CAPTURE_NUM_STATES entering state 2 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.540: [vfs7552] REQUEST CHUNK entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.540: Sending vfs7552_read_image_chunk 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.540: [vfs7552] REQUEST CHUNK completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.540: [vfs7552] CAPTURE_NUM_STATES entering state 3 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.540: [vfs7552] CAPTURE_NUM_STATES entering state 4 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.540: Cleaning image 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.540: variance_after = 18 261s 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.540: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.540: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.540: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.541: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.541: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.541: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.541: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.541: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.541: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.541: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.541: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.542: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.542: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.542: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.542: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.542: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.542: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.542: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.542: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.543: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.543: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.543: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.543: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.543: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.543: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.543: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.543: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.544: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.544: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.544: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.544: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.544: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.544: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.544: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.544: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.544: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.544: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.545: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.545: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.545: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.545: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.545: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.545: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.545: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.545: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.546: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.546: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.546: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.546: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.546: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.546: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.546: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.546: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.546: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.546: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.546: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.546: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.546: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.546: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.547: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.547: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.547: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.547: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.547: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.547: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.547: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.547: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.548: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.548: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.548: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.548: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.548: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.548: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.548: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.548: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.549: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.549: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.549: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.549: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.549: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.549: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.549: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.549: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.550: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.550: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.550: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.550: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.550: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.550: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.550: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.550: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.550: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.550: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.551: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.551: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.551: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.551: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.551: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.551: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.551: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.551: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.552: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.552: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.552: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.552: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.552: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.552: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.552: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.552: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.553: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.553: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.553: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.553: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.553: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.553: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.553: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.553: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.553: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.553: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.553: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.553: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.553: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.553: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.554: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.554: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.554: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.554: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.554: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.554: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.554: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.554: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.555: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.555: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.555: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.555: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.555: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.555: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.555: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.555: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.556: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.556: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.556: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.556: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.556: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.556: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.556: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.556: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.556: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.556: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.557: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.557: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.557: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.557: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.557: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.557: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.557: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.557: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.558: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.558: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.558: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.558: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.558: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.558: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.558: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.558: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.559: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.559: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.559: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.559: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.559: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.559: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.559: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.559: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.559: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.559: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.559: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.559: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.559: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.559: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.560: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.560: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.560: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.560: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.560: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.560: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.560: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.560: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.561: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.561: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.561: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.561: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.561: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.561: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.561: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.561: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.562: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.562: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.562: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.562: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.562: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.562: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.562: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.562: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.562: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.562: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.563: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.563: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.563: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.563: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.563: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.563: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.563: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.563: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.564: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.564: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.564: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.564: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.564: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.564: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.564: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.564: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.565: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.565: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.565: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.565: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.565: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.565: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.565: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.565: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.565: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.565: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.565: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.565: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.565: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.565: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.566: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.566: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.566: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.566: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.566: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.566: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.566: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.566: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.567: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.567: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.567: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.567: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.567: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.567: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.567: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.567: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.567: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.567: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.568: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.568: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.568: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.568: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.568: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.568: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.568: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.568: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.569: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.569: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.569: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.569: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.569: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.569: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.569: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.569: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.570: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.570: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.570: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.570: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.570: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.570: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.570: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.570: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.570: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.570: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.570: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.570: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.570: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.570: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.571: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.571: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.571: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.571: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.571: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.571: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.571: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.571: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.572: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.572: Receiving 64 bytes 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.572: Got 6 bytes out of 64 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.572: [vfs7552] QUERY DATA READY completed successfully 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.572: [vfs7552] CAPTURE_NUM_STATES entering state 1 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.572: [vfs7552] CAPTURE_NUM_STATES entering state 0 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.572: [vfs7552] QUERY DATA READY entering state 0 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.572: Sending vfs7552_is_image_ready 261s (process:1992): libfprint-SSM-DEBUG: 17:02:19.573: [vfs7552] QUERY DATA READY entering state 1 261s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.573: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.573: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.573: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.573: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.573: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.573: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.573: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.573: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.573: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.574: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.574: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.574: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.574: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.574: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.574: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.574: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.574: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.575: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.575: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.575: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.575: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.575: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.575: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.575: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.575: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.575: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.575: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.576: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.576: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.576: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.576: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.576: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.576: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.576: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.576: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.576: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.576: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.576: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.576: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.577: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.577: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.577: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.577: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.577: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.577: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.577: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.577: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.578: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.578: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.578: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.578: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.578: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.578: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.578: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.578: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.578: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.579: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.579: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.579: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.579: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.579: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.579: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.579: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.579: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.579: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.580: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.580: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.580: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.580: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.580: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.580: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.580: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.580: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.581: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.581: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.581: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.581: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.581: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.581: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.581: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.581: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.582: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.582: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.582: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.582: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.582: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.582: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.582: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.582: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.583: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.583: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.583: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.583: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.583: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.583: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.583: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.583: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.583: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.583: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.583: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.583: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.583: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.583: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.584: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.584: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.584: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.584: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.584: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.584: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.584: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.584: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.585: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.585: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.585: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.585: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.585: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.585: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.585: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.585: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.585: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.586: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.586: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.586: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.586: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.586: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.586: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.586: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.586: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.586: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.587: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.587: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.587: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.587: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.587: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.587: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.587: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.587: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.588: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.588: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.588: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.588: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.588: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.588: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.588: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.588: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.589: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.589: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.589: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.589: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.589: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.589: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.589: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.589: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.590: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.590: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.590: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.590: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.590: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.590: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.590: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.590: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.590: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.590: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.590: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.590: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.590: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.590: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.591: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.591: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.591: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.591: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.591: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.591: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.591: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.591: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.592: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.592: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.592: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.592: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.592: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.592: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.592: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.592: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.593: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.593: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.593: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.593: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.593: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.593: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.593: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.593: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.594: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.594: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.594: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.594: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.594: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.594: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.594: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.594: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.594: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.594: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.595: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.595: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.595: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.595: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.595: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.595: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.595: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.595: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.596: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.596: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.596: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.596: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.596: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.596: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.596: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.596: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.596: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.597: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.597: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.597: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.597: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.597: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.597: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.597: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.597: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.597: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.597: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.597: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.597: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.597: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.598: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.598: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.598: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.598: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.598: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.598: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.598: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.598: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.599: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.599: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.599: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.599: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.599: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.599: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.599: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.599: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.599: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.599: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.600: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.600: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.600: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.600: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.600: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.600: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.600: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.600: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.601: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.601: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.601: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.601: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.601: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.601: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.601: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.601: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.602: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.602: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.602: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.602: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.602: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.602: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.602: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.602: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.602: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.602: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.602: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.602: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.602: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.602: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.603: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.603: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.603: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.603: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.603: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.603: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.603: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.603: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.604: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.604: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.604: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.604: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.604: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.604: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.604: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.604: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.605: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.605: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.605: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.605: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.605: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.605: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.605: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.605: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.606: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.606: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.606: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.606: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.606: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.606: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.606: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.606: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.606: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.606: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.607: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.607: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.607: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.607: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.607: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.607: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.607: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.607: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.608: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.608: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.608: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.608: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.608: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.608: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.608: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.608: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.609: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.609: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.609: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.609: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.609: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.609: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.609: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.609: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.610: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.610: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.610: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.610: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.610: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.610: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.610: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.610: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.610: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.610: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.610: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.610: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.610: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.610: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.611: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.611: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.611: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.611: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.611: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.611: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.611: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.611: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.612: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.612: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.612: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.612: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.612: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.612: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.612: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.612: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.613: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.613: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.613: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.613: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.613: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.613: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.613: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.613: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.614: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.614: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.614: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.614: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.614: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.614: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.614: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.614: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.614: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.614: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.615: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.615: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.615: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.615: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.615: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.615: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.615: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.615: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.616: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.616: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.616: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.616: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.616: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.616: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.616: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.616: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.616: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.616: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.616: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.616: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.617: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.617: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.617: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.617: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.617: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.617: [vfs7552] CAPTURE_NUM_STATES entering state 2 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.617: [vfs7552] REQUEST CHUNK entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.617: Sending vfs7552_read_image_chunk 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.618: [vfs7552] REQUEST CHUNK completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.618: [vfs7552] CAPTURE_NUM_STATES entering state 3 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.618: [vfs7552] CAPTURE_NUM_STATES entering state 2 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.618: [vfs7552] REQUEST CHUNK entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.618: Sending vfs7552_read_image_chunk 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.619: [vfs7552] REQUEST CHUNK completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.619: [vfs7552] CAPTURE_NUM_STATES entering state 3 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.619: [vfs7552] CAPTURE_NUM_STATES entering state 2 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.619: [vfs7552] REQUEST CHUNK entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.619: Sending vfs7552_read_image_chunk 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.619: [vfs7552] REQUEST CHUNK completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.620: [vfs7552] CAPTURE_NUM_STATES entering state 3 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.620: [vfs7552] CAPTURE_NUM_STATES entering state 4 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.620: Cleaning image 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.620: variance_after = 18 262s 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.620: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.620: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.620: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.620: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.620: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.621: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.621: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.621: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.621: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.621: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.621: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.621: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.621: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.622: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.622: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.622: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.622: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.622: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.622: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.622: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.622: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.622: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.622: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.622: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.622: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.622: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.622: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.623: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.623: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.623: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.623: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.623: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.623: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.623: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.623: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.624: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.624: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.624: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.624: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.624: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.624: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.624: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.624: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.625: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.625: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.625: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.625: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.625: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.625: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.625: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.625: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.625: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.626: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.626: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.626: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.626: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.626: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.626: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.626: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.626: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.626: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.627: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.627: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.627: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.627: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.627: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.627: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.627: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.627: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.628: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.628: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.628: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.628: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.628: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.628: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.628: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.628: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.628: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.628: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.628: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.628: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.628: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.628: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.629: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.629: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.629: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.629: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.629: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.629: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.629: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.629: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.630: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.630: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.630: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.630: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.630: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.630: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.630: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.630: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.631: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.631: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.631: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.631: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.631: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.631: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.631: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.631: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.632: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.632: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.632: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.632: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.632: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.632: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.632: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.632: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.632: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.632: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.633: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.633: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.633: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.633: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.633: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.633: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.633: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.634: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.634: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.634: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.634: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.634: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.634: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.634: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.634: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.635: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.635: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.635: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.635: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.635: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.635: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.635: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.635: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.635: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.635: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.635: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.635: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.635: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.635: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.636: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.636: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.636: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.636: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.636: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.636: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.636: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.636: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.637: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.637: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.637: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.637: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.637: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.637: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.637: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.637: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.637: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.637: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.638: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.638: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.638: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.638: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.638: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.638: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.638: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.638: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.639: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.639: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.639: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.639: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.639: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.639: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.639: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.639: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.640: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.640: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.640: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.640: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.640: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.640: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.640: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.640: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.640: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.640: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.640: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.640: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.640: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.641: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.641: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.641: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.641: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.641: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.641: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.641: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.641: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.641: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.642: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.642: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.642: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.642: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.642: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.642: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.642: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.642: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.643: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.643: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.643: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.643: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.643: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.643: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.643: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.643: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.643: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.643: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.644: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.644: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.644: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.644: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.644: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.644: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.644: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.644: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.645: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.645: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.645: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.645: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.645: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.645: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.645: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.645: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.646: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.646: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.646: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.646: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.646: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.646: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.646: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.646: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.647: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.647: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.647: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.647: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.647: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.647: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.647: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.647: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.648: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.648: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.648: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.648: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.648: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.648: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.648: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.648: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.649: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.649: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.649: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.649: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.649: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.649: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.649: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.649: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.650: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.650: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.650: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.650: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.650: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.650: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.650: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.650: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.651: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.651: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.651: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.651: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.651: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.651: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.651: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.651: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.652: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.652: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.652: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.652: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.652: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.652: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.652: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.652: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.652: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.652: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.652: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.652: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.652: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.652: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.653: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.653: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.653: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.653: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.653: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.653: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.653: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.653: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.654: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.654: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.654: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.654: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.654: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.654: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.654: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.654: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.655: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.655: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.655: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.655: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.655: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.655: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.655: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.655: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.655: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.655: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.656: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.656: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.656: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.656: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.656: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.656: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.656: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.656: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.657: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.657: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.657: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.657: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.657: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.657: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.657: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.657: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.658: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.658: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.658: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.658: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.658: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.658: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.658: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.658: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.658: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.658: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.658: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.658: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.658: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.658: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.659: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.659: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.659: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.659: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.659: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.659: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.659: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.659: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.660: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.660: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.660: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.660: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.660: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.660: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.660: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.660: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.661: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.661: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.661: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.661: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.661: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.661: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.661: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.661: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.662: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.662: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.662: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.662: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.662: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.662: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.662: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.662: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.662: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.662: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.663: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.663: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.663: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.663: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.663: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.663: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.663: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.663: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.664: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.664: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.664: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.664: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.664: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.664: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.664: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.664: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.665: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.665: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.665: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.665: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.665: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.665: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.665: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.665: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.665: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.665: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.665: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.665: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.665: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.665: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.666: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.666: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.666: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.666: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.666: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.666: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.666: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.666: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.667: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.667: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.667: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.667: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.667: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.667: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.667: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.667: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.668: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.668: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.668: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.668: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.668: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.668: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.668: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.668: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.668: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.668: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.669: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.669: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.669: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.669: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.669: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.669: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.669: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.669: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.670: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.670: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.670: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.670: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.670: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.670: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.670: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.670: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.671: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.671: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.671: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.671: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.671: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.671: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.671: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.671: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.672: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.672: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.672: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.672: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.672: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.672: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.672: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.672: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.673: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.673: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.673: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.673: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.673: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.673: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.673: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.673: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.673: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.673: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.673: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.673: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.673: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.673: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.674: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.674: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.674: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.674: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.674: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.674: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.674: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.674: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.675: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.675: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.675: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.675: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.675: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.675: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.675: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.675: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.676: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.676: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.676: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.676: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.676: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.676: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.676: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.676: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.676: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.676: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.677: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.677: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.677: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.677: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.677: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.677: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.677: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.677: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.678: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.678: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.678: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.678: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.678: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.678: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.678: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.678: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.679: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.679: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.679: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.679: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.679: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.679: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.679: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.679: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.679: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.679: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.679: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.679: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.679: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.679: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.680: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.680: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.680: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.680: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.680: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.680: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.680: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.680: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.681: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.681: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.681: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.681: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.681: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.681: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.681: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.681: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.682: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.682: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.682: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.682: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.682: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.682: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.682: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.682: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.683: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.683: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.683: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.683: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.683: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.683: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.683: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.683: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.683: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.683: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.684: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.684: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.684: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.684: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.684: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.684: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.684: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.684: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.685: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.685: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.685: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.685: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.685: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.685: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.685: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.685: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.685: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.685: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.685: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.685: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.685: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.685: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.686: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.686: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.686: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.686: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.686: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.686: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.686: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.686: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.687: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.687: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.687: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.687: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.687: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.687: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.687: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.687: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.688: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.688: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.688: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.688: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.688: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.688: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.688: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.688: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.688: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.688: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.689: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.689: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.689: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.689: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.689: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.689: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.689: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.689: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.690: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.690: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.690: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.690: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.690: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.690: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.690: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.690: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.691: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.691: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.691: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.691: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.691: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.691: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.691: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.691: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.691: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.691: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.691: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.691: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.691: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.691: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.692: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.692: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.692: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.692: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.692: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.692: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.692: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.692: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.693: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.693: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.693: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.693: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.693: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.693: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.693: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.693: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.693: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.694: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.694: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.694: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.694: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.694: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.694: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.694: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.694: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.694: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.695: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.695: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.695: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.695: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.695: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.695: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.695: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.695: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.696: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.696: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.696: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.696: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.696: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.696: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.696: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.696: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.697: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.697: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.697: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.697: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.697: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.697: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.697: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.697: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.697: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.697: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.697: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.697: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.697: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.697: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.698: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.698: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.698: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.698: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.698: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.698: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.698: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.698: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.699: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.699: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.699: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.699: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.699: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.699: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.699: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.699: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.700: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.700: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.700: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.700: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.700: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.700: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.700: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.700: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.701: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.701: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.701: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.701: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.701: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.701: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.701: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.701: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.701: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.701: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.702: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.702: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.702: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.702: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.702: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.702: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.702: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.702: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.703: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.703: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.703: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.703: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.703: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.703: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.703: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.703: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.703: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.704: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.704: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.704: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.704: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.704: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.704: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.704: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.704: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.704: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.704: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.704: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.704: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.704: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.705: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.705: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.705: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.705: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.705: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.705: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.705: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.705: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.706: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.706: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.706: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.706: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.706: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.706: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.706: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.706: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.707: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.707: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.707: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.707: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.707: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.707: [vfs7552] CAPTURE_NUM_STATES entering state 2 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.707: [vfs7552] REQUEST CHUNK entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.707: Sending vfs7552_read_image_chunk 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.707: [vfs7552] REQUEST CHUNK completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.707: [vfs7552] CAPTURE_NUM_STATES entering state 3 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.708: [vfs7552] CAPTURE_NUM_STATES entering state 2 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.708: [vfs7552] REQUEST CHUNK entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.708: Sending vfs7552_read_image_chunk 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.708: [vfs7552] REQUEST CHUNK completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.708: [vfs7552] CAPTURE_NUM_STATES entering state 3 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.709: [vfs7552] CAPTURE_NUM_STATES entering state 2 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.709: [vfs7552] REQUEST CHUNK entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.709: Sending vfs7552_read_image_chunk 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.709: [vfs7552] REQUEST CHUNK completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.709: [vfs7552] CAPTURE_NUM_STATES entering state 3 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.710: [vfs7552] CAPTURE_NUM_STATES entering state 4 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.710: Cleaning image 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.710: variance_after = 18 262s 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.710: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.710: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.710: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.710: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.710: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.711: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.711: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.711: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.711: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.711: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.711: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.711: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.711: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.712: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.712: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.712: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.712: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.712: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.712: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.712: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.712: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.713: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.713: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.713: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.713: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.713: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.713: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.713: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.713: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.714: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.714: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.714: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.714: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.714: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.714: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.714: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.714: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.715: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.715: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.715: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.715: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.715: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.715: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.715: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.715: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.716: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.716: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.716: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.716: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.716: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.716: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.716: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.716: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.716: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.716: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.716: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.716: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.716: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.716: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.717: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.717: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.717: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.717: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.717: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.717: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.717: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.717: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.718: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.718: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.718: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.718: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.718: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.718: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.718: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.718: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.718: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.718: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.719: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.719: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.719: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.719: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.719: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.719: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.719: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.719: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.720: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.720: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.720: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.720: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.720: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.720: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.720: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.720: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.721: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.721: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.721: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.721: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.721: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.721: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.721: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.721: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.721: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.721: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.721: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.721: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.721: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.721: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.722: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.722: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.722: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.722: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.722: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.722: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.722: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.722: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.723: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.723: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.723: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.723: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.723: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.723: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.723: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.723: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.723: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.723: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.724: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.724: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.724: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.724: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.724: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.724: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.724: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.724: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.724: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.725: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.725: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.725: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.725: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.725: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.725: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.725: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.725: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.725: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.725: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.725: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.725: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.725: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.726: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.726: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.726: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.726: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.726: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.726: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.726: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.726: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.727: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.727: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.727: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.727: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.727: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.727: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.727: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.727: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.727: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.727: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.728: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.728: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.728: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.728: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.728: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.728: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.728: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.728: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.729: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.729: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.729: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.729: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.729: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.729: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.729: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.729: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.730: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.730: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.730: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.730: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.730: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.730: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.730: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.730: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.730: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.730: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.730: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.730: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.730: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.730: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.731: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.731: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.731: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.731: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.731: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.731: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.731: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.731: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.732: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.732: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.732: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.732: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.732: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.732: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.732: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.732: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.732: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.732: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.733: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.733: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.733: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.733: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.733: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.733: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.733: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.733: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.734: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.734: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.734: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.734: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.734: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.734: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.734: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.734: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.734: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.734: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.734: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.734: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.734: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.734: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.735: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.735: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.735: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.735: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.735: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.735: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.735: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.735: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.736: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.736: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.736: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.736: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.736: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.736: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.736: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.736: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.737: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.737: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.737: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.737: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.737: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.737: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.737: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.737: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.738: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.738: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.738: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.738: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.738: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.738: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.738: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.738: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.738: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.738: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.739: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.739: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.739: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.739: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.739: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.739: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.739: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.739: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.739: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.739: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.739: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.739: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.739: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.739: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.740: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.740: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.740: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.740: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.740: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.740: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.740: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.740: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.741: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.741: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.741: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.741: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.741: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.741: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.741: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.741: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.741: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.742: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.742: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.742: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.742: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.742: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.742: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.742: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.742: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.742: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.743: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.743: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.743: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.743: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.743: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.743: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.743: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.743: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.744: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.744: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.744: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.744: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.744: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.744: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.744: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.744: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.744: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.744: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.744: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.744: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.744: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.744: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.745: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.745: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.745: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.745: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.745: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.745: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.745: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.745: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.745: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.745: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.746: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.746: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.746: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.746: [vfs7552] CAPTURE_NUM_STATES entering state 2 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.746: [vfs7552] REQUEST CHUNK entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.746: Sending vfs7552_read_image_chunk 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.746: [vfs7552] REQUEST CHUNK completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.746: [vfs7552] CAPTURE_NUM_STATES entering state 3 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.747: [vfs7552] CAPTURE_NUM_STATES entering state 2 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.747: [vfs7552] REQUEST CHUNK entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.747: Sending vfs7552_read_image_chunk 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.747: [vfs7552] REQUEST CHUNK completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.747: [vfs7552] CAPTURE_NUM_STATES entering state 3 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.748: [vfs7552] CAPTURE_NUM_STATES entering state 2 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.748: [vfs7552] REQUEST CHUNK entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.748: Sending vfs7552_read_image_chunk 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.748: [vfs7552] REQUEST CHUNK completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.748: [vfs7552] CAPTURE_NUM_STATES entering state 3 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.749: [vfs7552] CAPTURE_NUM_STATES entering state 4 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.749: Cleaning image 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.749: variance_after = 17 262s 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.749: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.749: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.749: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.749: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.749: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.749: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.750: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.750: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.750: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.750: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.750: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.750: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.750: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.750: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.750: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.750: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.750: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.750: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.750: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.751: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.751: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.751: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.751: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.751: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.751: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.752: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.752: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.752: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.752: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.752: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.752: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.752: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.752: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.753: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.753: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.753: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.753: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.753: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.753: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.753: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.753: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.753: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.753: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.754: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.754: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.754: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.754: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.754: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.754: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.754: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.754: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.755: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.755: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.755: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.755: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.755: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.755: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.755: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.755: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.756: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.756: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.756: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.756: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.756: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.756: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.756: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.756: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.757: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.757: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.757: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.757: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.757: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.757: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.757: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.757: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.757: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.757: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.757: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.757: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.757: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.757: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.758: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.758: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.758: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.758: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.758: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.758: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.758: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.758: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.759: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.759: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.759: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.759: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.759: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.759: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.759: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.759: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.759: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.759: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.760: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.760: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.760: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.760: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.760: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.760: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.760: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.760: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.761: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.761: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.761: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.761: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.761: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.761: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.761: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.761: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.762: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.762: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.762: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.762: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.762: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.762: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.762: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.762: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.763: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.763: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.763: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.763: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.763: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.763: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.763: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.763: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.763: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.764: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.764: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.764: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.764: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.764: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.764: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.764: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.764: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.764: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.764: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.764: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.764: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.764: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.765: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.765: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.765: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.765: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.765: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.765: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.765: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.765: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.766: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.766: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.766: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.766: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.766: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.766: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.766: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.766: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.766: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.767: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.767: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.767: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.767: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.767: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.767: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.767: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.768: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.768: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.768: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.768: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.768: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.768: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.768: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.768: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.768: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.768: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.769: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.769: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.769: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.769: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.769: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.769: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.769: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.769: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.770: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.770: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.770: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.770: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.770: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.770: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.770: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.770: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.771: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.771: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.771: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.771: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.771: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.771: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.771: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.771: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.772: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.772: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.772: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.772: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.772: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.772: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.772: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.772: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.772: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.772: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.773: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.773: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.773: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.773: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.773: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.773: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.773: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.773: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.774: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.774: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.774: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.774: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.774: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.774: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.774: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.774: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.775: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.775: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.775: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.775: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.775: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.775: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.775: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.775: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.776: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.776: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.776: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.776: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.776: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.776: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.776: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.777: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.777: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.777: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.777: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.777: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.777: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.777: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.777: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.778: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.778: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.778: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.778: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.778: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.778: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.778: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.778: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.778: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.778: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.779: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.779: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.779: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.779: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.779: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.779: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.780: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.780: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.780: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.780: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.780: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.780: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.780: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.780: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.781: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.781: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.781: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.781: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.781: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.781: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.781: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.781: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.782: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.782: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.782: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.782: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.782: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.782: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.782: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.782: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.782: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.782: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.783: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.783: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.783: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.783: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.783: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.783: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.783: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.784: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.784: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.784: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.784: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.784: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.784: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.784: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.784: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.784: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.784: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.784: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.784: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.784: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.784: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.785: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.785: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.785: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.785: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.785: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.785: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.785: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.785: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.786: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.786: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.786: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.786: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.786: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.786: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.786: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.786: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.787: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.787: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.787: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.787: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.787: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.787: [vfs7552] CAPTURE_NUM_STATES entering state 2 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.787: [vfs7552] REQUEST CHUNK entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.787: Sending vfs7552_read_image_chunk 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.787: [vfs7552] REQUEST CHUNK completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.787: [vfs7552] CAPTURE_NUM_STATES entering state 3 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.788: [vfs7552] CAPTURE_NUM_STATES entering state 2 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.788: [vfs7552] REQUEST CHUNK entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.788: Sending vfs7552_read_image_chunk 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.788: [vfs7552] REQUEST CHUNK completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.788: [vfs7552] CAPTURE_NUM_STATES entering state 3 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.789: [vfs7552] CAPTURE_NUM_STATES entering state 2 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.789: [vfs7552] REQUEST CHUNK entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.789: Sending vfs7552_read_image_chunk 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.789: [vfs7552] REQUEST CHUNK completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.789: [vfs7552] CAPTURE_NUM_STATES entering state 3 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.790: [vfs7552] CAPTURE_NUM_STATES entering state 4 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.790: Cleaning image 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.790: variance_after = 16 262s 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.790: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.790: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.790: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.790: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.790: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.791: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.791: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.791: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.791: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.791: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.791: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.791: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.791: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.791: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.791: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.791: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.791: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.791: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.791: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.792: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.792: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.792: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.792: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.792: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.792: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.792: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.792: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.793: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.793: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.793: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.793: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.793: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.793: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.793: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.793: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.794: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.794: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.794: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.794: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.794: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.794: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.794: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.794: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.794: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.795: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.795: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.795: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.795: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.795: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.795: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.795: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.795: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.795: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.796: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.796: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.796: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.796: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.796: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.796: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.796: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.797: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.797: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.797: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.797: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.797: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.797: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.797: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.797: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.798: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.798: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.798: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.798: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.798: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.798: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.798: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.798: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.798: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.798: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.798: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.798: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.798: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.798: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.799: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.799: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.799: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.799: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.799: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.799: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.799: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.799: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.800: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.800: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.800: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.800: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.800: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.800: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.800: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.800: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.801: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.801: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.801: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.801: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.801: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.801: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.801: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.801: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.801: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.801: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.802: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.802: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.802: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.802: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.802: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.802: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.802: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.802: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.803: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.803: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.803: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.803: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.803: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.803: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.803: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.803: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.803: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.803: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.803: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.803: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.803: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.803: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.804: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.804: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.804: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.804: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.804: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.804: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.804: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.804: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.805: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.805: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.805: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.805: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.805: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.805: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.805: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.805: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.806: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.806: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.806: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.806: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.806: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.806: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.806: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.806: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.806: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.806: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.807: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.807: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.807: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.807: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.807: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.807: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.807: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.807: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.808: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.808: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.808: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.808: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.808: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.808: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.808: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.808: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.809: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.809: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.809: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.809: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.809: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.809: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.809: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.809: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.809: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.809: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.809: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.809: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.809: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.809: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.810: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.810: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.810: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.810: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.810: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.810: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.810: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.810: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.811: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.811: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.811: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.811: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.811: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.811: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.811: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.811: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.811: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.811: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.812: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.812: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.812: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.812: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.812: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.812: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.812: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.812: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.813: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.813: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.813: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.813: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.813: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.813: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.813: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.813: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.813: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.813: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.813: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.813: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.813: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.813: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.814: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.814: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.814: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.814: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.814: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.814: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.814: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.814: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.815: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.815: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.815: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.815: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.815: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.815: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.815: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.815: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.816: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.816: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.816: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.816: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.816: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.816: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.816: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.816: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.816: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.816: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.817: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.817: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.817: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.817: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.817: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.817: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.817: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.817: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.818: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.818: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.818: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.818: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.818: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.818: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.818: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.818: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.818: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.818: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.818: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.818: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.818: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.818: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.819: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.819: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.819: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.819: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.819: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.819: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.819: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.819: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.820: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.820: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.820: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.820: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.820: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.820: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.820: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.820: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.821: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.821: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.821: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.821: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.821: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.821: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.821: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.821: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.821: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.821: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.822: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.822: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.822: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.822: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.822: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.822: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.822: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.822: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.823: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.823: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.823: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.823: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.823: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.823: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.823: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.823: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.824: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.824: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.824: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.824: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.824: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.824: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.824: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.824: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.824: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.824: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.824: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.824: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.824: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.824: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.825: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.825: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.825: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.825: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.825: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.825: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.825: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.825: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.826: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.826: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.826: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.826: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.826: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.826: [vfs7552] CAPTURE_NUM_STATES entering state 2 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.826: [vfs7552] REQUEST CHUNK entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.826: Sending vfs7552_read_image_chunk 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.827: [vfs7552] REQUEST CHUNK completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.827: [vfs7552] CAPTURE_NUM_STATES entering state 3 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.827: [vfs7552] CAPTURE_NUM_STATES entering state 2 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.827: [vfs7552] REQUEST CHUNK entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.827: Sending vfs7552_read_image_chunk 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.828: [vfs7552] REQUEST CHUNK completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.828: [vfs7552] CAPTURE_NUM_STATES entering state 3 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.828: [vfs7552] CAPTURE_NUM_STATES entering state 2 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.828: [vfs7552] REQUEST CHUNK entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.828: Sending vfs7552_read_image_chunk 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.828: [vfs7552] REQUEST CHUNK completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.828: [vfs7552] CAPTURE_NUM_STATES entering state 3 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.829: [vfs7552] CAPTURE_NUM_STATES entering state 4 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.829: Cleaning image 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.829: variance_after = 17 262s 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.829: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.829: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.829: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.829: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.829: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.830: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.830: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.830: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.830: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.830: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.830: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.830: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.830: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.831: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.831: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.831: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.831: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.831: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.831: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.831: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.831: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.831: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.831: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.831: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.831: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.832: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.832: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.832: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.832: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.832: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.832: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.832: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.832: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.832: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.832: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.833: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.833: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.833: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.833: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.833: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.833: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.833: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.833: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.834: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.834: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.834: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.834: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.834: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.834: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.834: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.834: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.835: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.835: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.835: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.835: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.835: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.835: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.835: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.835: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.836: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.836: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.836: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.836: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.836: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.836: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.836: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.836: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.837: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.837: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.837: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.837: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.837: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.837: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.837: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.837: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.838: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.838: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.838: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.838: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.838: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.838: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.838: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.838: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.838: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.838: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.838: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.838: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.838: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.838: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.839: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.839: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.839: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.839: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.839: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.839: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.839: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.839: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.840: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.840: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.840: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.840: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.840: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.840: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.840: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.840: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.841: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.841: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.841: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.841: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.841: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.841: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.841: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.841: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.842: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.842: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.842: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.842: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.842: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.842: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.842: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.842: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.843: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.843: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.843: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.843: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.843: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.843: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.843: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.844: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.844: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.844: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.844: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.844: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.844: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.844: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.844: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.845: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.845: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.845: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.845: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.845: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.845: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.845: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.845: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.845: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.845: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.846: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.846: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.846: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.846: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.846: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.846: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.846: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.846: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.847: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.847: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.847: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.847: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.847: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.847: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.847: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.847: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.848: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.848: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.848: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.848: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.848: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.848: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.848: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.848: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.849: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.849: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.849: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.849: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.849: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.849: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.849: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.849: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.850: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.850: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.850: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.850: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.850: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.850: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.850: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.850: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.850: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.850: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.850: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.850: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.850: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.850: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.851: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.851: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.851: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.851: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.851: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.851: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.851: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.851: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.852: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.852: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.852: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.852: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.852: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.852: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.852: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.852: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.853: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.853: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.853: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.853: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.853: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.853: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.853: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.853: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.853: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.853: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.854: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.854: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.854: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.854: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.854: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.854: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.854: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.854: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.855: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.855: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.855: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.855: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.855: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.855: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.855: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.855: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.855: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.855: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.855: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.855: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.855: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.855: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.856: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.856: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.856: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.856: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.856: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.856: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.856: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.856: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.857: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.857: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.857: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.857: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.857: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.857: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.857: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.857: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.858: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.858: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.858: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.858: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.858: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.858: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.858: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.858: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.859: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.859: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.859: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.859: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.859: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.859: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.859: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.859: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.859: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.859: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.860: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.860: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.860: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.860: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.860: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.860: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.860: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.860: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.861: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.861: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.861: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.861: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.861: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.861: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.861: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.861: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.861: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.861: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.861: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.861: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.861: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.861: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.862: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.862: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.862: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.862: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.862: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.862: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.862: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.862: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.863: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.863: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.863: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.863: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.863: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.863: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.863: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.863: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.864: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.864: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.864: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.864: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.864: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.864: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.864: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.864: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.864: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.864: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.865: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.865: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.865: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.865: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.865: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.865: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.865: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.865: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.866: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.866: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.866: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.866: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.866: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.866: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.866: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.866: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.866: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.866: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.866: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.866: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.866: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.866: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.867: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.867: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.867: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.867: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.867: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.867: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.867: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.867: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.868: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.868: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.868: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.868: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.868: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.868: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.868: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.868: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.868: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.869: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.869: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.869: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.869: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.869: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.869: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.869: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.869: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.869: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.870: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.870: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.870: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.870: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.870: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.870: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.870: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.870: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.871: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.871: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.871: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.871: [vfs7552] CAPTURE_NUM_STATES entering state 2 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.871: [vfs7552] REQUEST CHUNK entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.871: Sending vfs7552_read_image_chunk 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.871: [vfs7552] REQUEST CHUNK completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.871: [vfs7552] CAPTURE_NUM_STATES entering state 3 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.871: [vfs7552] CAPTURE_NUM_STATES entering state 2 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.871: [vfs7552] REQUEST CHUNK entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.871: Sending vfs7552_read_image_chunk 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.872: [vfs7552] REQUEST CHUNK completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.872: [vfs7552] CAPTURE_NUM_STATES entering state 3 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.872: [vfs7552] CAPTURE_NUM_STATES entering state 2 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.872: [vfs7552] REQUEST CHUNK entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.872: Sending vfs7552_read_image_chunk 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.873: [vfs7552] REQUEST CHUNK completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.873: [vfs7552] CAPTURE_NUM_STATES entering state 3 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.873: [vfs7552] CAPTURE_NUM_STATES entering state 4 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.873: Cleaning image 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.873: variance_after = 17 262s 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.873: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.873: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.873: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.874: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.874: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.874: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.874: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.874: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.874: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.874: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.874: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.874: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.874: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.875: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.875: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.875: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.875: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.875: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.875: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.875: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.875: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.876: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.876: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.876: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.876: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.876: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.876: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.876: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.876: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.876: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.876: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.876: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.876: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.876: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.876: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.877: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.877: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.877: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.877: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.877: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.877: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.877: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.877: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.878: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.878: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.878: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.878: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.878: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.878: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.878: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.878: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.878: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.879: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.879: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.879: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.879: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.879: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.879: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.879: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.879: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.879: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.880: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.880: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.880: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.880: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.880: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.880: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.880: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.880: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.881: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.881: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.881: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.881: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.881: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.881: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.881: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.881: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.882: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.882: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.882: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.882: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.882: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.882: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.882: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.882: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.882: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.882: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.882: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.882: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.882: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.882: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.883: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.883: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.883: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.883: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.883: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.883: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.883: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.883: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.884: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.884: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.884: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.884: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.884: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.884: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.884: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.884: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.884: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.884: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.885: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.885: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.885: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.885: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.885: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.885: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.885: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.885: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.886: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.886: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.886: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.886: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.886: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.886: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.886: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.886: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.887: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.887: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.887: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.887: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.887: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.887: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.887: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.887: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.887: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.887: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.887: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.887: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.887: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.887: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.888: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.888: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.888: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.888: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.888: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.888: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.888: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.888: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.889: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.889: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.889: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.889: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.889: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.889: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.889: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.889: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.890: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.890: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.890: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.890: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.890: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.890: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.890: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.890: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.890: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.890: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.891: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.891: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.891: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.891: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.891: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.891: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.891: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.891: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.892: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.892: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.892: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.892: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.892: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.892: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.892: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.892: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.892: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.892: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.892: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.892: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.892: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.892: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.893: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.893: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.893: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.893: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.893: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.893: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.893: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.893: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.894: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.894: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.894: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.894: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.894: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.894: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.894: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.894: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.895: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.895: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.895: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.895: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.895: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.895: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.895: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.895: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.896: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.896: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.896: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.896: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.896: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.896: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.896: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.896: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.896: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.896: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.897: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.897: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.897: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.897: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.897: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.897: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.897: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.897: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.898: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.898: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.898: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.898: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.898: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.898: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.898: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.898: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.898: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.898: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.898: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.898: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.898: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.898: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.899: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.899: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.899: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.899: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.899: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.899: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.899: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.899: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.900: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.900: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.900: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.900: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.900: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.900: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.900: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.900: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.901: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.901: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.901: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.901: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.901: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.901: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.901: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.901: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.901: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.901: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.902: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.902: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.902: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.902: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.902: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.902: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.902: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.902: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.903: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.903: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.903: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.903: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.903: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.903: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.903: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.903: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.903: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.903: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.903: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.903: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.903: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.903: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.904: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.904: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.904: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.904: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.904: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.904: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.904: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.904: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.905: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.905: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.905: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.905: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.905: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.905: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.905: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.905: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.906: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.906: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.906: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.906: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.906: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.906: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.906: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.906: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.906: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.906: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.907: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.907: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.907: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.907: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.907: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.907: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.907: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.907: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.908: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.908: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.908: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.908: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.908: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.908: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.908: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.908: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.909: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.909: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.909: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.909: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.909: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.909: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.909: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.909: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.910: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.910: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.910: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.910: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.910: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.910: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.910: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.910: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.910: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.910: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.910: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.910: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.910: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.910: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.911: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.911: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.911: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.911: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.911: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.911: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.911: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.911: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.912: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.912: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.912: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.912: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.912: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.912: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.912: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.912: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.913: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.913: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.913: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.913: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.913: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.913: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.913: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.913: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.913: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.913: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.914: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.914: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.914: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.914: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.914: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.914: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.914: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.914: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.915: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.915: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.915: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.915: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.915: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.915: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.915: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.915: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.916: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.916: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.916: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.916: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.916: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.916: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.916: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.916: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.916: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.916: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.916: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.916: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.916: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.916: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.917: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.917: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.917: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.917: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.917: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.917: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.917: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.917: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.918: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.918: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.918: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.918: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.918: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.918: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.918: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.918: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.918: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.918: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.919: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.919: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.919: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.919: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.919: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.919: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.919: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.920: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.920: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.920: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.920: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.920: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.920: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.920: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.920: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.921: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.921: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.921: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.921: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.921: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.921: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.921: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.921: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.921: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.921: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.921: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.921: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.921: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.921: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.922: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.922: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.922: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.922: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.922: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.922: [vfs7552] CAPTURE_NUM_STATES entering state 2 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.922: [vfs7552] REQUEST CHUNK entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.922: Sending vfs7552_read_image_chunk 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.923: [vfs7552] REQUEST CHUNK completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.923: [vfs7552] CAPTURE_NUM_STATES entering state 3 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.923: [vfs7552] CAPTURE_NUM_STATES entering state 2 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.923: [vfs7552] REQUEST CHUNK entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.923: Sending vfs7552_read_image_chunk 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.924: [vfs7552] REQUEST CHUNK completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.924: [vfs7552] CAPTURE_NUM_STATES entering state 3 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.924: [vfs7552] CAPTURE_NUM_STATES entering state 2 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.924: [vfs7552] REQUEST CHUNK entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.924: Sending vfs7552_read_image_chunk 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.925: [vfs7552] REQUEST CHUNK completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.925: [vfs7552] CAPTURE_NUM_STATES entering state 3 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.925: [vfs7552] CAPTURE_NUM_STATES entering state 4 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.925: Cleaning image 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.925: variance_after = 17 262s 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.925: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.925: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.925: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.926: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.926: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.926: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.926: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.926: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.926: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.926: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.926: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.926: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.926: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.927: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.927: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.927: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.927: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.927: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.927: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.927: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.927: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.928: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.928: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.928: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.928: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.928: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.928: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.928: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.928: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.929: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.929: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.929: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.929: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.929: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.929: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.929: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.929: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.929: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.929: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.929: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.930: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.930: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.930: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.930: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.930: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.930: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.930: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.930: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.930: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.931: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.931: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.931: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.931: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.931: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.931: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.931: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.931: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.932: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.932: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.932: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.932: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.932: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.932: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.932: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.932: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.933: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.933: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.933: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.933: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.933: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.933: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.933: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.933: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.933: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.934: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.934: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.934: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.934: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.934: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.934: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.934: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.934: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.934: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.935: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.935: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.935: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.935: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.935: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.935: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.936: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.936: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.936: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.936: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.936: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.936: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.936: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.936: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.937: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.937: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.937: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.937: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.937: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.937: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.937: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.937: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.938: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.938: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.938: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.938: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.938: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.938: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.938: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.938: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.938: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.938: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.938: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.938: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.938: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.938: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.939: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.939: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.939: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.939: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.939: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.939: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.939: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.939: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.940: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.940: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.940: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.940: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.940: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.940: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.940: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.940: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.941: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.941: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.941: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.941: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.941: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.941: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.941: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.941: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.941: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.941: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.942: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.942: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.942: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.942: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.942: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.942: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.942: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.942: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.943: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.943: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.943: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.943: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.943: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.943: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.944: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.944: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.944: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.944: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.944: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.944: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.944: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.944: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.944: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.944: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.944: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.944: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.944: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.944: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.945: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.945: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.945: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.945: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.945: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.945: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.945: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.945: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.946: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.946: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.946: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.946: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.946: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.946: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.946: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.946: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.946: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.947: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.947: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.947: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.947: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.947: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.947: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.947: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.947: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.948: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.948: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.948: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.948: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.948: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.948: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.948: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.948: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.948: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.949: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.949: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.949: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.949: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.949: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.949: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.949: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.949: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.949: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.949: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.949: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.950: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.950: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.950: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.950: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.950: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.950: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.950: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.950: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.950: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.951: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.951: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.951: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.951: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.951: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.951: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.951: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.951: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.952: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.952: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.952: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.952: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.952: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.952: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.952: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.952: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.953: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.953: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.953: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.953: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.953: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.953: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.953: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.953: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.954: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.954: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.954: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.954: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.954: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.954: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.954: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.954: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.954: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.954: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.955: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.955: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.955: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.955: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.955: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.955: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.955: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.955: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.956: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.956: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.956: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.956: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.956: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.956: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.956: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.956: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.957: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.957: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.957: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.957: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.957: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.957: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.957: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.957: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.957: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.957: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.957: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.957: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.957: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.957: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.958: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.958: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.958: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.958: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.958: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.958: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.958: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.958: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.959: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.959: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.959: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.959: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.959: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.959: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.959: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.959: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.960: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.960: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.960: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.960: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.960: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.960: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.960: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.960: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.961: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.961: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.961: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.961: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.961: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.961: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.961: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.961: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.962: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.962: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.962: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.962: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.962: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.962: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.962: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.962: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.962: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.962: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.963: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.963: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.963: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.963: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.963: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.963: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.963: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.963: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.964: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.964: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.964: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.964: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.964: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.964: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.964: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.964: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.965: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.965: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.965: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.965: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.965: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.965: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.965: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.965: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.966: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.966: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.966: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.966: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.966: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.966: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.966: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.966: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.966: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.966: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.966: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.966: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.966: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.966: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.967: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.967: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.967: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.967: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.967: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.967: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.967: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.967: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.968: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.968: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.968: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.968: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.968: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.968: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.968: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.968: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.969: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.969: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.969: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.969: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.969: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.969: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.969: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.969: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.970: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.970: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.970: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.970: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.970: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.970: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.970: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.970: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.970: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.970: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.971: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.971: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.971: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.971: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.971: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.971: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.971: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.971: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.972: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.972: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.972: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.972: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.972: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.972: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.972: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.972: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.973: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.973: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.973: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.973: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.973: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.973: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.973: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.973: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.974: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.974: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.974: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.974: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.974: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.974: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.974: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.974: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.975: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.975: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.975: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.975: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.975: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.975: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.975: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.975: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.976: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.976: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.976: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.976: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.976: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.976: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.976: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.976: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.976: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.976: [vfs7552] QUERY DATA READY completed successfully 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.976: [vfs7552] CAPTURE_NUM_STATES entering state 1 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.976: [vfs7552] CAPTURE_NUM_STATES entering state 0 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.976: [vfs7552] QUERY DATA READY entering state 0 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.977: Sending vfs7552_is_image_ready 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.977: [vfs7552] QUERY DATA READY entering state 1 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.977: Receiving 64 bytes 262s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.977: Got 6 bytes out of 64 262s (process:1992): libfprint-SSM-DEBUG: 17:02:19.977: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.977: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.977: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.977: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.978: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.978: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.978: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.978: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.978: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.978: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.978: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.978: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.979: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.979: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.979: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.979: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.979: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.979: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.979: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.979: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.980: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.980: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.980: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.980: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.980: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.980: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.980: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.980: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.980: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.980: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.981: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.981: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.981: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.981: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.981: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.981: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.981: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.981: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.982: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.982: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.982: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.982: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.982: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.982: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.982: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.982: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.983: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.983: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.983: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.983: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.983: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.983: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.983: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.983: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.984: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.984: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.984: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.984: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.984: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.984: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.984: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.984: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.984: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.984: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.985: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.985: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.985: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.985: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.985: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.985: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.985: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.985: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.986: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.986: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.986: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.986: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.986: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.986: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.986: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.986: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.987: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.987: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.987: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.987: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.987: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.987: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.987: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.987: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.988: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.988: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.988: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.988: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.988: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.988: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.988: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.988: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.989: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.989: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.989: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.989: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.989: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.989: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.989: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.989: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.989: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.990: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.990: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.990: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.990: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.990: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.990: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.990: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.990: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.990: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.991: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.991: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.991: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.991: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.991: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.991: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.991: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.991: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.992: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.992: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.992: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.992: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.992: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.992: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.992: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.992: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.993: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.993: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.993: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.993: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.993: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.993: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.993: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.993: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.994: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.994: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.994: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.994: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.994: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.994: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.994: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.994: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.995: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.995: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.995: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.995: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.995: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.995: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.995: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.995: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.996: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.996: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.996: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.996: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.996: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.996: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.996: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.996: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.997: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.997: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.997: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.997: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.997: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.997: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.997: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.997: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.997: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.997: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.997: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.997: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.997: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.997: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.998: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.998: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.998: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.998: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.998: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.998: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.998: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.998: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.999: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.999: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.999: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.999: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.999: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.999: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:19.999: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:19.999: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.000: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.000: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.000: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.000: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.000: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.000: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.000: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.000: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.000: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.000: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.001: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.001: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.001: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.001: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.001: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.001: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.001: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.001: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.002: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.002: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.002: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.002: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.002: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.002: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.002: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.002: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.003: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.003: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.003: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.003: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.003: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.003: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.003: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.003: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.004: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.004: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.004: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.004: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.004: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.004: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.004: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.004: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.004: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.004: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.004: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.004: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.004: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.004: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.005: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.005: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.005: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.005: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.005: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.005: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.005: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.005: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.006: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.006: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.006: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.006: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.006: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.006: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.006: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.006: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.007: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.007: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.007: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.007: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.007: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.007: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.007: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.007: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.008: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.008: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.008: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.008: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.008: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.008: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.008: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.008: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.008: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.008: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.009: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.009: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.009: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.009: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.009: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.009: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.009: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.009: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.010: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.010: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.010: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.010: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.010: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.010: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.010: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.010: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.011: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.011: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.011: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.011: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.011: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.011: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.011: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.011: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.012: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.012: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.012: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.012: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.012: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.012: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.012: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.012: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.013: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.013: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.013: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.013: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.013: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.013: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.013: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.013: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.014: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.014: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.014: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.014: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.014: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.014: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.014: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.014: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.014: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.014: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.014: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.015: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.015: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.015: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.015: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.015: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.015: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.015: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.015: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.015: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.015: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.015: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.016: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.016: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.016: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.016: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.016: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.016: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.016: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.016: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.017: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.017: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.017: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.017: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.017: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.017: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.017: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.017: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.018: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.018: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.018: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.018: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.018: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.018: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.018: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.018: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.019: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.019: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.019: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.019: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.019: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.019: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.019: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.019: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.020: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.020: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.020: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.020: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.020: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.020: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.020: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.020: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.020: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.020: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.021: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.021: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.021: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.021: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.021: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.021: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.021: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.021: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.022: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.022: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.022: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.022: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.022: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.022: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.022: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.022: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.023: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.023: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.023: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.023: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.023: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.023: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.023: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.023: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.024: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.024: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.024: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.024: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.024: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.024: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.024: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.024: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.024: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.024: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.024: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.024: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.024: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.024: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.025: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.025: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.025: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.025: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.025: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.025: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.025: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.025: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.026: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.026: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.026: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.026: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.026: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.026: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.026: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.026: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.027: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.027: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.027: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.027: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.027: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.027: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.027: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.027: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.027: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.027: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.028: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.028: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.028: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.028: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.028: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.028: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.028: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.029: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.029: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.029: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.029: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.029: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.029: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.029: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.029: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.030: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.030: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.030: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.030: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.030: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.030: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.030: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.030: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.030: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.031: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.031: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.031: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.031: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.031: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.031: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.031: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.031: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.031: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.031: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.031: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.031: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.031: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.032: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.032: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.032: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.032: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.032: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.032: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.032: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.032: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.033: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.033: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.033: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.033: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.033: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.033: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.033: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.033: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.034: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.034: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.034: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.034: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.034: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.034: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.034: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.034: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.035: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.035: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.035: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.035: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.035: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.035: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.035: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.035: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.035: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.035: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.036: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.036: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.036: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.036: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.036: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.036: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.036: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.037: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.037: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.037: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.037: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.037: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.037: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.037: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.038: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.038: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.038: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.038: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.038: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.038: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.038: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.038: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.038: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.039: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.039: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.039: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.039: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.039: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.039: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.039: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.039: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.039: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.040: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.040: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.040: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.040: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.040: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.040: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.040: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.040: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.041: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.041: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.041: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.041: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.041: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.041: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.041: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.041: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.042: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.042: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.042: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.042: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.042: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.042: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.042: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.042: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.042: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.042: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.042: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.042: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.042: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.042: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.043: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.043: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.043: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.043: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.043: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.043: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.043: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.043: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.044: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.044: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.044: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.044: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.044: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.044: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.044: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.044: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.044: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.044: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.045: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.045: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.045: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.045: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.045: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.045: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.045: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.045: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.046: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.046: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.046: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.046: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.046: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.046: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.046: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.046: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.047: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.047: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.047: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.047: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.047: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.047: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.047: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.047: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.047: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.047: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.047: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.048: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.048: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.048: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.048: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.048: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.048: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.048: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.048: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.048: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.048: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.048: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.049: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.049: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.049: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.049: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.049: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.049: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.049: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.049: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.049: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.049: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.050: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.050: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.050: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.050: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.050: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.050: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.050: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.050: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.051: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.051: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.051: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.051: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.051: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.051: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.051: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.051: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.052: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.052: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.052: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.052: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.052: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.052: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.052: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.052: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.052: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.052: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.052: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.052: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.052: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.052: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.053: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.053: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.053: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.053: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.053: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.053: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.053: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.053: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.054: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.054: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.054: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.054: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.054: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.054: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.054: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.054: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.054: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.054: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.055: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.055: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.055: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.055: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.055: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.055: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.055: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.055: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.056: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.056: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.056: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.056: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.056: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.056: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.056: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.056: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.056: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.056: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.056: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.057: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.057: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.057: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.057: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.057: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.058: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.058: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.058: [vfs7552] CAPTURE_NUM_STATES entering state 4 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.058: Cleaning image 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.058: variance_after = 20 263s 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.058: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.058: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.058: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.059: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.059: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.059: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.059: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.059: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.059: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.059: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.059: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.059: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.059: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.060: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.060: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.060: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.060: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.060: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.060: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.060: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.060: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.061: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.061: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.061: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.061: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.061: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.061: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.061: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.061: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.062: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.062: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.062: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.062: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.062: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.062: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.062: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.062: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.062: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.062: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.062: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.062: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.062: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.062: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.063: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.063: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.063: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.063: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.063: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.063: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.063: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.063: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.064: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.064: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.064: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.064: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.064: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.064: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.064: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.064: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.065: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.065: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.065: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.065: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.065: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.065: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.065: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.065: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.065: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.065: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.066: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.066: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.066: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.066: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.066: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.066: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.067: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.067: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.067: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.067: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.067: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.067: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.067: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.067: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.068: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.068: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.068: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.068: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.068: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.068: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.068: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.068: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.068: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.068: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.068: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.068: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.068: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.068: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.069: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.069: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.069: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.069: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.069: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.069: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.069: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.069: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.070: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.070: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.070: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.070: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.070: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.070: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.070: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.070: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.070: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.070: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.071: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.071: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.071: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.071: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.071: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.071: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.071: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.071: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.072: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.072: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.072: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.072: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.072: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.072: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.072: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.072: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.072: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.072: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.072: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.072: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.072: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.072: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.073: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.073: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.073: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.073: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.073: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.073: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.073: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.073: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.074: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.074: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.074: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.074: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.074: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.074: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.074: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.074: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.074: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.074: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.075: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.075: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.075: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.075: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.075: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.075: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.075: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.075: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.076: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.076: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.076: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.076: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.076: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.076: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.076: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.076: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.076: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.076: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.076: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.076: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.076: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.076: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.077: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.077: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.077: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.077: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.077: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.077: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.077: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.077: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.078: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.078: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.078: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.078: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.078: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.078: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.078: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.078: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.078: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.078: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.079: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.079: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.079: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.079: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.079: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.079: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.079: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.079: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.080: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.080: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.080: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.080: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.080: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.080: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.080: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.080: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.081: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.081: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.081: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.081: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.081: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.081: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.081: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.081: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.082: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.082: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.082: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.082: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.082: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.082: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.082: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.082: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.082: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.082: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.082: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.082: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.082: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.082: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.083: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.083: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.083: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.083: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.083: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.083: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.083: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.083: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.084: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.084: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.084: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.084: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.084: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.084: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.084: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.084: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.085: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.085: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.085: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.085: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.085: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.085: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.085: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.085: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.085: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.085: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.086: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.086: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.086: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.086: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.086: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.086: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.086: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.086: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.087: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.087: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.087: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.087: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.087: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.087: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.087: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.087: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.088: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.088: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.088: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.088: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.088: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.088: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.088: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.088: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.088: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.088: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.088: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.088: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.088: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.088: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.089: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.089: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.089: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.089: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.089: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.089: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.089: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.089: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.090: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.090: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.090: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.090: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.090: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.090: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.090: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.090: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.090: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.090: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.091: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.091: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.091: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.091: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.091: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.091: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.091: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.091: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.092: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.092: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.092: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.092: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.092: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.092: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.092: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.092: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.092: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.092: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.092: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.092: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.092: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.092: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.093: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.093: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.093: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.093: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.093: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.093: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.093: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.093: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.094: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.094: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.094: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.094: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.094: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.094: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.095: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.095: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.095: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.095: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.095: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.095: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.095: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.095: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.096: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.096: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.096: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.096: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.096: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.096: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.096: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.096: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.096: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.096: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.097: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.097: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.097: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.097: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.097: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.097: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.097: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.097: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.098: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.098: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.098: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.098: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.098: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.098: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.098: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.098: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.099: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.099: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.099: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.099: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.099: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.099: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.099: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.099: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.099: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.099: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.099: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.099: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.099: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.099: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.100: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.100: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.100: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.100: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.100: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.100: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.100: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.100: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.101: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.101: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.101: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.101: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.101: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.101: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.101: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.101: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.101: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.101: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.102: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.102: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.102: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.102: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.102: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.102: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.102: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.102: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.103: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.103: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.103: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.103: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.103: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.103: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.103: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.103: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.104: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.104: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.104: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.104: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.104: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.104: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.104: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.104: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.105: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.105: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.105: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.105: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.105: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.105: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.105: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.105: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.105: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.105: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.105: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.105: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.105: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.105: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.106: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.106: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.106: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.106: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.106: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.106: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.106: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.106: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.107: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.107: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.107: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.107: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.107: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.107: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.107: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.107: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.108: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.108: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.108: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.108: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.108: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.108: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.108: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.108: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.108: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.108: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.109: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.109: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.109: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.109: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.109: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.109: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.109: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.109: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.110: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.110: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.110: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.110: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.110: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.110: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.110: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.110: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.110: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.110: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.110: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.110: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.110: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.110: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.111: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.111: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.111: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.111: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.111: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.111: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.111: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.111: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.112: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.112: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.112: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.112: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.112: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.112: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.112: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.112: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.113: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.113: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.113: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.113: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.113: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.113: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.113: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.113: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.113: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.113: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.114: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.114: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.114: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.114: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.114: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.114: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.114: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.114: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.115: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.115: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.115: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.115: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.115: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.115: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.115: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.115: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.116: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.116: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.116: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.116: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.116: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.116: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.116: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.116: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.117: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.117: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.117: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.117: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.117: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.117: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.117: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.117: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.117: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.117: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.117: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.117: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.118: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.118: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.118: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.118: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.118: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.118: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.118: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.118: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.118: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.118: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.119: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.119: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.119: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.119: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.119: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.119: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.119: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.119: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.120: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.120: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.120: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.120: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.120: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.120: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.120: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.120: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.120: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.120: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.121: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.121: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.121: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.121: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.121: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.121: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.121: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.121: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.122: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.122: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.122: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.122: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.122: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.122: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.122: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.122: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.123: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.123: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.123: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.123: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.123: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.123: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.123: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.123: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.124: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.124: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.124: [vfs7552] CAPTURE_NUM_STATES entering state 4 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.124: Cleaning image 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.124: variance_after = 17 263s 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.124: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.124: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.124: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.125: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.125: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.125: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.125: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.125: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.125: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.125: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.125: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.126: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.126: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.126: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.126: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.126: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.126: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.126: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.126: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.127: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.127: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.127: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.127: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.127: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.127: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.127: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.127: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.127: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.127: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.128: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.128: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.128: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.128: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.128: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.128: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.128: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.128: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.129: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.129: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.129: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.129: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.129: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.129: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.129: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.129: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.130: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.130: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.130: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.130: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.130: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.130: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.130: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.130: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.130: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.130: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.130: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.130: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.130: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.130: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.131: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.131: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.131: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.131: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.131: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.131: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.131: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.131: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.132: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.132: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.132: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.132: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.132: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.132: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.132: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.132: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.133: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.133: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.133: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.133: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.133: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.133: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.133: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.133: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.134: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.134: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.134: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.134: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.134: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.134: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.134: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.134: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.134: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.134: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.135: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.135: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.135: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.135: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.135: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.135: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.135: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.135: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.136: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.136: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.136: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.136: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.136: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.136: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.136: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.136: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.136: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.136: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.136: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.136: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.136: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.137: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.137: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.137: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.137: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.137: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.137: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.137: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.137: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.138: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.138: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.138: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.138: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.138: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.138: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.138: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.138: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.138: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.138: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.139: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.139: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.139: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.139: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.139: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.139: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.139: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.139: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.140: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.140: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.140: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.140: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.140: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.140: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.140: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.140: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.141: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.141: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.141: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.141: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.141: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.141: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.141: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.141: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.141: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.141: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.142: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.142: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.142: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.142: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.142: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.142: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.142: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.142: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.143: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.143: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.143: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.143: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.143: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.143: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.143: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.144: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.144: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.144: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.144: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.144: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.144: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.144: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.144: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.145: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.145: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.145: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.145: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.145: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.145: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.145: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.145: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.146: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.146: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.146: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.146: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.146: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.146: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.146: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.146: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.147: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.147: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.147: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.147: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.147: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.147: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.147: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.147: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.147: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.147: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.148: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.148: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.148: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.148: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.148: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.148: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.148: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.149: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.149: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.149: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.149: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.149: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.149: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.149: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.149: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.150: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.150: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.150: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.150: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.150: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.150: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.150: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.150: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.150: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.150: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.151: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.151: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.151: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.151: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.151: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.151: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.152: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.152: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.152: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.152: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.152: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.152: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.152: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.152: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.153: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.153: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.153: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.153: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.153: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.153: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.153: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.153: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.153: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.154: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.154: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.154: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.154: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.154: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.154: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.154: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.154: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.154: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.155: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.155: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.155: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.155: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.155: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.155: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.155: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.156: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.156: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.156: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.156: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.156: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.156: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.156: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.156: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.157: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.157: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.157: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.157: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.157: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.157: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.157: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.157: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.157: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.157: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.158: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.158: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.158: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.158: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.158: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.158: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.158: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.159: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.159: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.159: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.159: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.159: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.159: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.159: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.159: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.159: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.160: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.160: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.160: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.160: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.160: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.160: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.161: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.161: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.161: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.161: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.161: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.161: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.161: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.161: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.161: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.161: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.161: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.161: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.161: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.161: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.162: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.162: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.162: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.162: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.162: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.162: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.162: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.163: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.163: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.163: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.163: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.163: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.163: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.163: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.163: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.163: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.163: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.164: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.164: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.164: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.164: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.164: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.164: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.164: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.164: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.165: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.165: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.165: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.165: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.165: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.165: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.165: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.165: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.166: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.166: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.166: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.166: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.166: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.166: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.166: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.166: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.166: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.166: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.166: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.167: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.167: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.167: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.167: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.167: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.168: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.168: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.168: [vfs7552] CAPTURE_NUM_STATES entering state 4 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.168: Cleaning image 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.168: variance_after = 17 263s 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.168: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.168: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.168: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.169: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.169: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.169: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.169: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.169: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.169: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.169: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.169: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.170: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.170: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.170: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.170: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.170: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.170: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.171: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.171: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.171: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.171: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.171: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.171: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.172: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.172: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.172: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.172: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.172: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.172: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.172: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.172: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.172: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.172: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.173: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.173: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.173: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.173: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.173: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.173: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.173: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.173: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.174: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.174: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.174: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.174: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.174: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.174: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.174: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.174: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.175: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.175: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.175: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.175: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.175: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.175: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.175: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.175: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.175: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.175: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.175: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.175: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.175: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.175: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.176: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.176: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.176: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.176: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.176: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.176: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.176: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.176: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.177: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.177: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.177: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.177: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.177: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.177: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.177: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.177: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.178: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.178: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.178: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.178: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.178: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.178: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.178: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.179: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.179: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.179: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.179: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.179: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.179: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.179: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.179: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.180: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.180: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.180: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.180: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.180: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.180: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.180: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.180: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.180: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.180: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.181: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.181: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.181: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.181: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.181: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.181: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.181: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.181: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.182: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.182: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.182: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.182: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.182: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.182: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.182: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.182: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.182: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.182: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.183: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.183: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.183: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.183: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.183: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.183: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.184: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.184: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.184: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.184: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.184: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.184: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.184: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.184: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.185: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.185: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.185: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.185: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.185: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.185: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.185: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.185: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.185: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.185: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.185: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.185: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.185: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.185: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.186: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.186: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.186: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.186: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.186: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.186: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.186: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.187: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.187: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.187: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.187: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.187: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.187: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.187: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.187: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.187: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.187: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.188: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.188: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.188: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.188: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.188: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.188: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.189: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.189: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.189: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.189: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.189: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.189: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.189: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.189: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.189: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.189: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.189: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.189: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.189: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.189: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.190: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.190: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.190: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.190: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.190: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.190: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.190: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.190: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.191: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.191: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.191: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.191: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.191: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.191: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.191: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.191: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.191: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.191: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.192: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.192: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.192: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.192: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.192: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.192: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.192: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.192: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.193: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.193: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.193: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.193: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.193: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.193: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.193: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.193: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.193: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.193: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.194: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.194: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.194: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.194: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.194: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.194: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.194: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.194: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.195: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.195: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.195: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.195: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.195: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.195: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.195: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.196: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.196: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.196: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.196: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.196: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.196: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.196: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.196: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.197: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.197: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.197: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.197: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.197: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.197: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.197: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.197: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.197: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.197: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.198: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.198: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.198: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.198: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.198: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.198: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.198: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.198: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.199: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.199: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.199: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.199: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.199: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.199: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.200: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.200: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.200: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.200: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.200: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.200: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.200: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.200: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.200: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.200: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.200: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.200: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.200: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.200: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.201: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.201: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.201: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.201: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.201: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.201: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.201: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.201: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.202: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.202: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.202: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.202: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.202: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.202: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.203: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.203: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.203: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.203: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.203: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.203: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.204: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.204: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.204: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.204: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.204: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.204: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.204: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.204: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.204: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.204: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.205: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.205: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.205: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.205: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.205: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.205: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.205: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.205: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.206: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.206: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.206: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.206: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.206: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.206: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.206: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.206: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.207: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.207: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.207: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.207: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.207: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.207: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.207: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.208: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.208: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.208: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.208: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.208: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.208: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.208: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.208: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.208: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.208: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.209: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.209: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.209: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.209: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.209: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.210: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.210: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.210: [vfs7552] CAPTURE_NUM_STATES entering state 4 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.210: Cleaning image 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.210: variance_after = 17 263s 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.210: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.210: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.210: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.211: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.211: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.211: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.211: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.211: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.211: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.211: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.211: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.212: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.212: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.212: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.212: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.212: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.212: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.212: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.213: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.213: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.213: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.213: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.213: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.213: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.213: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.213: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.213: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.213: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.214: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.214: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.214: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.214: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.214: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.214: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.214: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.215: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.215: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.215: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.215: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.215: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.215: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.215: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.215: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.216: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.216: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.216: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.216: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.216: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.216: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.216: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.216: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.216: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.216: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.217: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.217: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.217: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.217: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.217: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.217: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.217: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.217: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.218: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.218: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.218: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.218: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.218: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.218: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.218: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.218: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.219: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.219: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.219: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.219: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.219: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.219: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.219: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.219: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.220: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.220: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.220: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.220: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.220: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.220: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.220: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.221: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.221: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.221: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.221: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.221: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.221: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.221: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.221: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.221: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.222: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.222: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.222: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.222: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.222: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.222: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.222: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.222: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.223: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.223: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.223: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.223: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.223: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.223: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.224: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.224: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.224: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.224: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.224: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.224: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.224: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.224: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.225: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.225: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.225: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.225: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.225: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.225: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.225: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.225: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.226: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.226: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.226: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.226: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.226: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.226: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.226: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.227: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.227: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.227: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.227: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.227: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.227: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.227: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.227: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.228: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.228: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.228: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.228: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.228: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.228: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.228: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.229: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.229: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.229: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.229: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.229: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.229: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.229: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.229: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.229: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.229: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.229: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.229: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.229: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.230: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.230: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.230: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.230: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.230: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.230: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.230: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.230: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.231: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.231: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.231: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.231: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.231: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.231: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.231: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.231: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.232: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.232: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.232: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.232: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.232: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.232: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.232: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.232: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.233: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.233: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.233: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.233: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.233: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.233: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.234: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.234: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.234: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.234: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.234: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.234: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.234: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.234: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.235: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.235: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.235: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.235: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.235: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.235: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.235: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.235: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.236: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.236: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.236: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.236: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.236: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.236: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.236: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.236: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.237: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.237: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.237: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.237: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.237: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.237: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.237: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.237: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.238: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.238: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.238: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.238: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.238: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.238: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.238: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.238: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.239: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.239: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.239: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.239: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.239: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.239: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.239: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.239: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.240: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.240: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.240: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.240: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.240: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.240: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.240: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.240: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.241: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.241: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.241: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.241: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.241: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.241: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.241: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.241: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.242: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.242: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.242: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.242: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.242: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.242: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.242: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.242: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.243: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.243: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.243: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.243: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.243: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.243: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.243: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.243: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.244: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.244: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.244: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.244: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.244: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.244: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.244: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.244: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.244: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.245: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.245: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.245: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.245: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.245: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.245: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.245: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.245: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.245: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.245: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.245: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.245: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.245: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.246: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.246: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.246: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.246: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.246: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.246: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.246: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.246: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.247: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.247: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.247: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.247: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.247: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.247: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.247: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.247: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.248: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.248: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.248: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.248: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.248: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.248: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.248: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.249: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.249: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.249: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.249: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.249: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.249: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.249: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.250: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.250: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.250: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.250: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.251: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.251: [vfs7552] CAPTURE_NUM_STATES entering state 4 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.251: Cleaning image 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.251: variance_after = 17 263s 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.251: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.251: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.251: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.252: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.252: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.252: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.252: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.252: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.252: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.252: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.252: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.252: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.252: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.253: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.253: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.253: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.253: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.253: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.253: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.253: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.253: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.254: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.254: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.254: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.254: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.254: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.254: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.254: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.254: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.255: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.255: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.255: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.255: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.255: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.255: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.255: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.255: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.256: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.256: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.256: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.256: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.256: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.256: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.256: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.256: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.256: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.256: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.256: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.256: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.256: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.256: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.257: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.257: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.257: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.257: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.257: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.257: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.257: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.257: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.258: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.258: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.258: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.258: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.258: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.258: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.258: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.258: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.259: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.259: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.259: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.259: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.259: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.259: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.259: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.259: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.260: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.260: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.260: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.260: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.260: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.260: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.260: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.260: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.261: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.261: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.261: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.261: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.261: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.261: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.261: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.261: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.261: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.261: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.262: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.262: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.262: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.262: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.262: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.262: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.262: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.262: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.263: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.263: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.263: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.263: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.263: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.263: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.263: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.263: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.264: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.264: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.264: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.264: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.264: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.264: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.264: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.264: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.265: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.265: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.265: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.265: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.265: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.265: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.265: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.265: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.266: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.266: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.266: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.266: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.266: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.266: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.266: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.266: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.266: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.266: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.266: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.266: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.266: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.266: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.267: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.267: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.267: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.267: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.267: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.267: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.267: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.267: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.268: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.268: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.268: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.268: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.268: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.268: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.268: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.268: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.269: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.269: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.269: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.269: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.269: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.269: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.269: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.269: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.270: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.270: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.270: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.270: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.270: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.270: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.270: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.270: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.271: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.271: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.271: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.271: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.271: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.271: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.271: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.271: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.271: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.271: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.272: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.272: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.272: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.272: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.272: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.272: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.272: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.272: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.273: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.273: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.273: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.273: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.273: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.273: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.273: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.273: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.274: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.274: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.274: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.274: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.274: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.274: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.274: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.274: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.275: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.275: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.275: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.275: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.275: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.275: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.275: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.275: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.275: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.276: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.276: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.276: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.276: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.276: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.276: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.276: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.276: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.276: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.276: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.276: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.276: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.276: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.277: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.277: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.277: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.277: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.277: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.277: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.277: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.277: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.278: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.278: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.278: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.278: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.278: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.278: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.278: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.278: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.279: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.279: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.279: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.279: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.279: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.279: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.279: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.279: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.279: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.279: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.280: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.280: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.280: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.280: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.280: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.280: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.280: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.280: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.281: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.281: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.281: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.281: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.281: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.281: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.281: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.281: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.282: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.282: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.282: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.282: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.282: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.282: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.282: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.282: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.283: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.283: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.283: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.283: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.283: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.283: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.283: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.283: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.284: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.284: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.284: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.284: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.284: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.284: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.284: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.284: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.285: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.285: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.285: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.285: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.285: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.285: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.285: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.285: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.285: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.285: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.285: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.285: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.285: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.285: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.286: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.286: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.286: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.286: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.286: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.286: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.286: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.286: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.287: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.287: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.287: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.287: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.287: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.287: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.287: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.287: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.288: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.288: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.288: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.288: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.288: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.288: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.288: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.288: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.289: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.289: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.289: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.289: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.289: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.289: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.289: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.289: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.290: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.290: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.290: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.290: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.290: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.290: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.290: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.290: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.290: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.290: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.291: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.291: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.291: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.291: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.291: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.291: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.291: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.291: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.292: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.292: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.292: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.292: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.292: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.292: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.292: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.292: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.293: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.293: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.293: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.293: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.293: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.294: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.294: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.294: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.294: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.294: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.295: [vfs7552] CAPTURE_NUM_STATES entering state 4 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.295: Cleaning image 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.295: variance_after = 16 263s 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.295: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.295: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.295: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.295: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.295: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.296: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.296: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.296: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.296: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.296: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.296: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.296: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.296: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.297: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.297: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.297: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.297: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.297: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.297: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.297: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.297: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.297: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.297: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.297: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.297: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.297: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.297: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.298: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.298: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.298: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.298: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.298: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.298: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.298: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.298: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.299: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.299: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.299: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.299: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.299: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.299: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.299: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.299: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.300: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.300: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.300: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.300: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.300: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.300: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.300: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.300: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.301: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.301: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.301: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.301: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.301: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.301: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.301: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.301: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.302: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.302: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.302: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.302: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.302: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.302: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.302: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.302: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.302: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.302: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.303: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.303: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.303: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.303: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.303: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.303: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.303: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.303: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.304: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.304: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.304: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.304: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.304: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.304: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.304: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.304: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.305: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.305: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.305: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.305: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.305: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.305: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.305: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.305: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.306: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.306: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.306: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.306: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.306: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.306: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.306: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.306: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.307: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.307: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.307: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.307: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.307: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.307: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.307: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.307: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.307: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.308: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.308: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.308: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.308: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.308: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.308: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.308: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.308: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.308: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.308: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.308: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.308: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.308: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.309: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.309: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.309: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.309: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.309: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.309: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.309: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.309: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.310: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.310: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.310: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.310: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.310: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.310: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.310: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.310: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.311: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.311: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.311: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.311: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.311: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.311: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.311: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.311: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.312: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.312: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.312: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.312: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.312: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.312: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.312: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.312: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.313: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.313: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.313: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.313: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.313: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.313: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.313: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.313: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.313: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.313: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.314: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.314: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.314: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.314: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.314: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.314: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.315: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.315: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.315: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.315: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.315: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.315: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.315: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.315: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.316: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.316: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.316: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.316: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.316: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.316: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.316: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.316: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.317: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.317: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.317: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.317: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.317: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.317: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.317: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.317: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.317: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.317: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.318: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.318: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.318: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.318: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.318: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.318: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.319: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.319: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.319: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.319: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.319: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.319: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.319: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.319: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.320: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.320: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.320: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.320: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.320: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.320: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.320: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.320: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.321: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.321: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.321: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.321: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.321: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.321: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.321: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.321: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.322: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.322: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.322: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.322: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.322: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.322: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.322: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.322: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.322: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.322: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.323: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.323: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.323: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.323: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.323: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.323: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.323: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.323: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.324: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.324: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.324: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.324: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.324: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.324: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.324: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.324: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.324: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.324: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.324: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.324: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.324: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.324: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.325: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.325: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.325: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.325: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.325: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.325: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.325: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.325: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.326: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.326: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.326: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.326: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.326: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.326: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.326: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.326: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.326: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.326: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.327: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.327: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.327: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.327: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.327: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.327: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.327: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.327: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.328: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.328: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.328: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.328: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.328: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.328: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.328: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.328: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.328: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.328: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.328: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.328: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.328: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.328: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.329: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.329: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.329: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.329: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.329: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.329: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.329: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.329: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.330: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.330: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.330: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.330: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.330: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.330: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.330: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.330: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.331: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.331: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.331: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.331: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.331: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.331: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.331: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.331: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.331: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.331: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.332: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.332: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.332: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.332: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.332: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.332: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.332: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.332: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.333: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.333: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.333: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.333: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.333: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.333: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.333: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.333: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.333: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.333: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.333: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.333: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.333: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.333: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.334: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.334: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.334: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.334: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.334: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.334: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.334: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.334: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.335: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.335: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.335: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.335: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.335: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.336: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.336: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.336: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.336: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.336: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.337: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.337: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.337: [vfs7552] CAPTURE_NUM_STATES entering state 4 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.337: Cleaning image 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.337: variance_after = 17 263s 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.337: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.337: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.337: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.338: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.338: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.338: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.338: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.338: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.338: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.338: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.338: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.338: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.338: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.339: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.339: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.339: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.339: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.339: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.339: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.339: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.339: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.340: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.340: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.340: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.340: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.340: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.340: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.340: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.340: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.340: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.340: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.340: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.340: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.340: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.340: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.341: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.341: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.341: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.341: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.341: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.341: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.341: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.341: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.342: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.342: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.342: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.342: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.342: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.342: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.342: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.342: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.342: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.342: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.343: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.343: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.343: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.343: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.343: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.343: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.343: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.343: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.344: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.344: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.344: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.344: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.344: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.344: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.344: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.344: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.344: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.344: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.344: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.344: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.344: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.345: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.345: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.345: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.345: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.345: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.345: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.345: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.345: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.345: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.346: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.346: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.346: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.346: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.346: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.346: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.346: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.346: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.347: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.347: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.347: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.347: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.347: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.347: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.347: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.347: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.347: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.347: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.348: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.348: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.348: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.348: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.348: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.348: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.348: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.348: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.349: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.349: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.349: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.349: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.349: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.349: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.349: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.349: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.350: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.350: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.350: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.350: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.350: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.350: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.350: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.350: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.350: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.350: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.350: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.350: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.350: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.350: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.351: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.351: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.351: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.351: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.351: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.351: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.351: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.351: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.352: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.352: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.352: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.352: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.352: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.352: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.352: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.352: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.352: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.352: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.353: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.353: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.353: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.353: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.353: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.353: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.353: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.353: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.354: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.354: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.354: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.354: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.354: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.354: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.354: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.354: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.354: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.354: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.354: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.354: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.354: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.354: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.355: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.355: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.355: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.355: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.355: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.355: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.355: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.355: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.356: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.356: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.356: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.356: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.356: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.356: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.356: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.356: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.357: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.357: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.357: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.357: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.357: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.357: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.357: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.357: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.357: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.357: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.358: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.358: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.358: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.358: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.358: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.358: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.358: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.358: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.359: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.359: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.359: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.359: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.359: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.359: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.359: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.359: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.359: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.359: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.359: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.359: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.359: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.359: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.360: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.360: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.360: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.360: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.360: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.360: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.360: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.360: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.361: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.361: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.361: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.361: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.361: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.361: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.361: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.361: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.361: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.361: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.362: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.362: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.362: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.362: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.362: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.362: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.362: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.362: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.363: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.363: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.363: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.363: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.363: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.363: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.363: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.363: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.364: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.364: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.364: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.364: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.364: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.364: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.364: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.364: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.364: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.364: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.364: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.364: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.364: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.364: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.365: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.365: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.365: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.365: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.365: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.365: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.365: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.365: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.366: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.366: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.366: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.366: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.366: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.366: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.366: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.366: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.367: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.367: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.367: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.367: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.367: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.367: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.367: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.367: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.367: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.367: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.368: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.368: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.368: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.368: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.368: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.368: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.368: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.368: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.369: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.369: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.369: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.369: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.369: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.369: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.369: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.369: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.369: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.369: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.369: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.369: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.369: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.369: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.370: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.370: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.370: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.370: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.370: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.370: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.370: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.370: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.371: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.371: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.371: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.371: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.371: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.371: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.371: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.371: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.372: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.372: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.372: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.372: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.372: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.372: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.372: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.373: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.373: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.373: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.373: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.373: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.374: [vfs7552] CAPTURE_NUM_STATES entering state 4 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.374: Cleaning image 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.374: variance_after = 16 263s 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.374: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.374: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.374: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.374: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.374: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.374: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.374: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.374: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.374: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.374: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.374: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.375: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.375: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.375: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.375: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.375: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.375: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.375: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.375: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.376: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.376: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.376: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.376: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.376: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.376: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.376: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.376: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.376: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.376: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.377: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.377: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.377: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.377: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.377: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.377: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.377: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.377: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.378: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.378: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.378: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.378: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.378: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.378: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.378: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.378: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.379: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.379: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.379: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.379: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.379: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.379: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.379: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.379: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.379: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.379: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.379: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.379: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.379: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.379: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.380: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.380: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.380: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.380: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.380: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.380: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.380: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.380: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.381: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.381: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.381: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.381: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.381: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.381: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.381: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.381: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.381: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.381: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.382: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.382: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.382: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.382: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.382: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.382: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.382: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.382: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.383: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.383: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.383: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.383: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.383: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.383: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.383: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.383: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.384: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.384: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.384: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.384: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.384: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.384: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.384: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.384: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.384: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.385: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.385: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.385: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.385: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.385: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.385: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.385: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.385: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.385: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.385: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.385: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.385: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.385: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.386: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.386: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.386: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.386: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.386: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.386: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.386: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.386: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.387: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.387: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.387: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.387: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.387: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.387: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.387: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.387: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.388: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.388: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.388: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.388: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.388: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.388: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.388: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.388: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.388: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.388: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.389: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.389: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.389: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.389: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.389: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.389: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.389: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.389: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.390: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.390: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.390: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.390: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.390: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.390: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.390: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.390: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.391: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.391: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.391: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.391: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.391: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.391: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.391: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.391: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.392: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.392: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.392: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.392: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.392: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.392: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.392: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.392: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.392: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.392: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.392: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.392: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.392: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.392: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.393: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.393: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.393: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.393: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.393: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.393: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.393: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.393: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.394: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.394: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.394: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.394: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.394: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.394: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.394: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.394: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.394: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.394: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.395: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.395: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.395: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.395: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.395: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.395: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.395: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.395: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.396: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.396: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.396: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.396: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.396: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.396: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.396: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.396: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.396: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.396: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.396: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.396: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.396: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.396: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.397: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.397: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.397: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.397: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.397: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.397: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.397: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.397: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.398: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.398: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.398: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.398: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.398: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.398: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.398: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.398: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.398: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.398: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.399: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.399: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.399: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.399: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.399: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.399: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.399: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.399: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.400: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.400: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.400: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.400: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.400: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.400: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.400: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.400: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.401: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.401: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.401: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.401: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.401: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.401: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.401: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.401: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.402: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.402: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.402: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.402: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.402: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.402: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.402: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.402: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.402: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.402: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.402: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.402: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.402: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.402: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.403: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.403: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.403: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.403: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.403: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.403: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.403: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.403: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.404: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.404: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.404: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.404: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.404: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.404: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.404: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.404: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.404: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.405: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.405: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.405: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.405: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.405: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.405: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.405: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.405: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.405: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.406: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.406: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.406: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.406: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.406: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.406: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.406: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.406: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.407: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.407: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.407: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.407: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.407: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.407: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.407: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.407: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.407: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.407: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.407: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.407: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.407: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.407: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.408: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.408: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.408: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.408: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.408: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.408: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.408: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.408: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.409: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.409: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.409: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.409: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.409: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.410: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.410: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.410: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.410: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.410: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.411: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.411: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.411: [vfs7552] CAPTURE_NUM_STATES entering state 4 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.411: Cleaning image 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.411: variance_after = 2168 263s 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.411: [vfs7552] CAPTURE_NUM_STATES completed successfully 263s (process:1992): libfprint-device-DEBUG: 17:02:20.411: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 263s (process:1992): libfprint-image_device-DEBUG: 17:02:20.411: Image device reported finger status: on 263s (process:1992): libfprint-image_device-DEBUG: 17:02:20.411: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.461: changing to 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.461: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.461: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.461: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.462: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.462: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.462: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.462: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.462: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.462: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.462: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.462: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.462: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.462: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.463: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.463: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.463: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.463: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.463: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.464: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.464: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.464: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.464: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.464: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.465: [vfs7552] CAPTURE_NUM_STATES entering state 4 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.465: Cleaning image 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.465: variance_after = 2082 263s 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.465: [vfs7552] CAPTURE_NUM_STATES completed successfully 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.465: Image captured 263s (process:1992): libfprint-image_device-DEBUG: 17:02:20.465: Image device captured an image 263s (process:1992): libfprint-image_device-DEBUG: 17:02:20.465: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 263s (process:1992): libfprint-device-DEBUG: 17:02:20.465: Device reported finger status change: FP_FINGER_STATUS_PRESENT 263s (process:1992): libfprint-image-DEBUG: 17:02:20.494: Minutiae scan completed in 0.028773 secs 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.515: changing to 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.515: [vfs7552] CAPTURE_NUM_STATES entering state 0 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.515: [vfs7552] QUERY DATA READY entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.515: Sending vfs7552_is_image_ready 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.516: [vfs7552] QUERY DATA READY entering state 1 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.516: Receiving 64 bytes 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.516: Got 6 bytes out of 64 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.516: [vfs7552] QUERY DATA READY completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.516: [vfs7552] CAPTURE_NUM_STATES entering state 1 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.516: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.516: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.516: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.517: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.517: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.517: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.517: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.517: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.518: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.518: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.518: [vfs7552] CAPTURE_NUM_STATES entering state 2 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.518: [vfs7552] REQUEST CHUNK entering state 0 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.518: Sending vfs7552_read_image_chunk 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.519: [vfs7552] REQUEST CHUNK completed successfully 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.519: [vfs7552] CAPTURE_NUM_STATES entering state 3 263s (process:1992): libfprint-SSM-DEBUG: 17:02:20.519: [vfs7552] CAPTURE_NUM_STATES entering state 4 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.519: Cleaning image 263s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.519: variance_after = 2003 263s 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.519: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.519: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.519: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.520: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.520: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.520: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.520: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.520: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.520: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.520: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.520: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.520: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.520: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.521: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.521: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.521: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.521: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.521: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.521: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.521: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.521: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.522: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.522: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.522: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.522: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.522: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.522: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.522: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.522: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.523: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.523: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.523: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.523: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.523: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.523: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.523: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.523: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.524: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.524: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.524: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.524: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.524: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.524: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.524: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.524: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.524: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.524: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.524: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.524: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.524: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.524: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.525: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.525: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.525: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.525: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.525: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.525: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.525: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.525: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.526: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.526: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.526: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.526: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.526: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.526: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.526: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.526: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.526: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.527: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.527: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.527: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.527: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.527: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.527: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.527: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.527: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.527: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.528: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.528: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.528: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.528: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.528: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.528: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.528: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.528: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.529: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.529: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.529: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.529: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.529: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.529: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.529: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.529: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.529: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.529: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.529: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.529: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.529: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.529: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.530: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.530: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.530: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.530: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.530: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.530: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.530: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.530: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.531: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.531: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.531: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.531: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.531: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.531: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.531: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.531: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.532: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.532: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.532: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.532: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.532: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.532: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.532: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.532: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.533: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.533: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.533: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.533: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.533: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.533: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.533: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.533: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.533: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.533: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.534: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.534: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.534: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.534: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.534: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.534: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.534: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.534: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.535: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.535: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.535: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.535: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.535: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.535: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.535: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.535: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.535: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.535: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.535: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.535: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.535: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.535: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.536: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.536: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.536: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.536: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.536: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.536: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.536: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.536: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.537: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.537: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.537: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.537: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.537: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.537: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.537: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.537: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.537: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.538: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.538: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.538: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.538: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.538: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.538: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.538: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.538: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.538: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.539: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.539: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.539: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.539: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.539: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.539: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.539: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.539: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.540: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.540: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.540: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.540: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.540: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.540: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.540: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.540: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.540: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.540: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.540: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.540: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.540: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.540: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.541: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.541: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.541: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.541: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.541: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.541: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.541: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.541: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.542: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.542: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.542: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.542: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.542: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.542: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.542: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.542: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.542: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.542: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.543: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.543: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.543: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.543: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.543: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.543: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.543: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.543: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.544: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.544: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.544: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.544: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.544: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.544: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.544: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.544: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.544: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.544: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.544: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.544: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.544: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.544: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.545: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.545: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.545: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.545: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.545: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.545: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.545: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.545: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.546: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.546: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.546: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.546: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.546: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.546: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.546: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.546: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.547: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.547: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.547: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.547: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.547: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.547: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.547: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.547: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.547: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.547: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.548: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.548: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.548: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.548: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.548: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.548: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.548: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.548: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.549: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.549: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.549: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.549: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.549: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.549: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.549: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.549: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.549: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.549: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.549: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.549: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.549: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.549: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.550: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.550: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.550: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.550: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.550: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.550: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.550: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.550: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.551: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.551: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.551: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.551: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.551: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.551: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.551: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.551: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.552: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.552: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.552: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.552: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.552: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.552: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.552: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.552: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.552: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.552: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.553: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.553: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.553: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.553: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.553: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.553: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.553: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.553: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.554: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.554: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.554: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.554: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.554: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.554: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.554: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.554: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.555: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.555: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.555: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.555: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.555: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.555: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.555: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.555: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.555: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.555: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.555: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.555: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.555: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.555: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.556: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.556: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.556: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.556: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.556: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.556: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.556: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.556: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.557: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.557: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.557: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.557: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.557: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.557: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.557: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.557: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.557: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.557: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.558: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.558: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.558: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.558: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.558: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.558: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.558: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.558: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.559: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.559: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.559: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.559: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.559: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.559: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.559: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.559: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.560: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.560: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.560: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.560: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.560: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.560: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.560: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.560: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.560: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.560: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.560: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.560: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.560: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.560: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.561: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.561: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.561: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.561: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.561: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.561: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.561: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.561: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.562: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.562: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.562: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.562: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.562: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.562: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.562: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.562: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.562: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.562: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.563: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.563: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.563: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.563: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.563: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.563: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.563: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.563: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.564: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.564: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.564: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.564: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.564: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.564: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.564: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.564: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.564: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.564: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.564: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.564: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.564: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.564: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.565: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.565: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.565: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.565: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.565: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.565: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.565: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.565: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.566: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.566: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.566: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.566: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.566: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.566: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.566: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.566: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.566: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.566: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.567: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.567: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.567: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.567: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.567: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.567: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.567: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.567: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.568: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.568: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.568: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.568: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.568: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.568: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.568: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.568: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.569: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.569: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.569: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.569: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.569: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.569: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.569: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.569: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.569: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.569: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.570: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.570: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.570: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.570: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.570: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.570: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.570: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.570: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.570: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.570: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.570: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.570: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.571: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.571: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.571: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.571: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.571: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.571: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.571: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.571: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.572: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.572: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.572: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.572: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.572: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.572: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.572: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.572: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.572: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.572: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.573: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.573: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.573: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.573: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.573: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.573: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.573: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.573: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.574: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.574: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.574: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.574: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.574: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.574: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.574: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.574: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.575: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.575: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.575: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.575: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.575: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.575: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.575: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.575: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.575: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.575: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.575: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.575: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.575: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.575: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.576: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.576: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.576: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.576: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.576: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.576: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.576: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.576: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.577: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.577: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.577: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.577: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.577: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.577: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.577: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.577: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.578: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.578: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.578: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.578: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.578: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.578: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.578: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.578: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.579: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.579: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.579: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.579: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.579: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.579: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.579: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.579: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.580: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.580: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.580: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.580: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.580: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.580: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.580: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.580: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.581: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.581: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.581: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.581: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.581: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.581: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.581: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.581: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.581: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.581: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.582: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.582: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.582: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.582: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.582: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.582: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.582: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.582: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.583: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.583: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.583: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.583: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.583: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.583: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.583: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.583: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.584: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.584: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.584: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.584: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.584: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.584: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.584: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.584: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.585: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.585: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.585: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.585: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.585: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.585: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.585: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.585: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.586: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.586: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.586: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.586: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.586: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.586: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.586: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.586: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.587: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.587: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.587: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.587: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.587: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.587: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.587: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.587: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.588: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.588: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.588: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.588: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.588: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.588: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.588: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.588: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.589: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.589: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.589: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.589: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.589: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.589: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.589: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.589: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.589: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.589: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.589: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.589: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.589: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.589: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.590: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.590: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.590: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.590: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.590: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.590: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.590: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.590: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.591: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.591: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.591: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.591: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.591: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.591: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.591: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.591: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.592: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.592: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.592: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.592: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.592: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.592: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.592: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.592: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.593: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.593: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.593: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.593: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.593: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.593: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.593: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.593: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.594: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.594: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.594: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.594: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.594: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.594: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.594: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.594: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.594: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.595: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.595: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.595: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.595: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.595: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.595: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.595: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.595: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.596: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.596: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.596: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.596: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.596: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.596: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.596: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.596: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.597: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.597: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.597: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.597: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.597: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.597: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.597: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.597: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.597: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.598: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.598: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.598: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.598: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.598: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.598: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.598: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.598: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.599: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.599: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.599: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.599: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.599: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.599: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.599: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.599: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.600: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.600: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.600: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.600: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.600: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.600: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.600: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.600: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.601: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.601: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.601: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.601: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.601: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.601: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.601: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.601: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.601: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.601: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.601: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.601: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.601: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.601: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.602: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.602: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.602: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.602: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.602: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.602: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.602: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.603: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.603: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.603: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.603: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.603: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.603: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.603: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.603: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.603: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.604: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.604: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.604: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.604: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.604: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.604: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.604: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.604: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.605: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.605: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.605: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.605: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.605: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.605: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.605: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.605: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.606: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.606: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.606: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.606: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.606: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.606: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.606: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.606: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.607: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.607: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.607: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.607: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.607: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.607: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.607: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.607: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.608: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.608: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.608: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.608: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.608: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.608: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.608: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.608: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.609: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.609: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.609: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.609: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.609: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.609: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.609: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.609: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.610: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.610: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.610: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.610: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.610: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.610: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.610: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.610: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.610: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.610: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.611: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.611: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.611: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.611: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.611: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.611: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.611: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.611: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.612: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.612: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.612: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.612: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.612: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.612: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.612: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.612: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.613: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.613: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.613: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.613: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.613: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.613: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.613: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.613: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.614: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.614: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.614: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.614: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.614: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.614: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.614: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.614: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.615: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.615: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.615: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.615: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.615: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.615: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.615: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.615: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.615: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.616: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.616: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.616: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.616: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.616: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.616: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.616: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.616: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.616: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.616: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.616: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.617: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.617: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.617: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.617: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.617: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.617: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.617: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.617: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.618: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.618: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.618: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.618: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.618: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.618: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.618: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.618: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.619: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.619: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.619: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.619: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.619: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.619: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.619: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.619: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.620: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.620: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.620: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.620: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.620: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.620: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.620: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.620: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.621: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.621: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.621: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.621: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.621: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.621: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.621: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.621: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.622: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.622: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.622: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.622: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.622: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.622: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.622: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.622: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.623: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.623: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.623: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.623: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.623: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.623: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.623: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.623: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.624: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.624: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.624: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.624: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.624: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.624: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.624: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.624: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.625: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.625: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.625: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.625: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.625: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.625: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.625: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.625: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.626: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.626: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.626: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.626: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.626: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.626: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.626: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.626: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.627: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.627: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.627: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.627: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.627: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.627: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.627: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.627: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.628: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.628: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.628: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.628: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.628: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.628: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.628: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.628: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.628: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.628: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.629: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.629: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.629: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.629: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.629: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.629: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.629: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.629: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.630: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.630: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.630: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.630: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.630: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.630: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.630: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.630: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.631: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.631: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.631: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.631: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.631: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.631: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.631: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.631: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.632: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.632: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.632: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.632: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.632: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.632: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.632: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.632: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.633: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.633: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.633: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.633: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.633: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.633: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.633: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.633: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.633: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.634: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.634: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.634: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.634: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.634: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.634: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.634: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.634: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.634: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.634: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.634: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.635: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.635: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.635: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.635: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.635: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.636: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.636: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.636: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.636: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.636: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.636: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.636: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.636: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.636: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.636: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.636: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.637: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.637: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.637: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.637: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.637: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.637: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.637: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.637: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.638: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.638: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.638: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.638: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.638: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.638: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.638: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.638: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.639: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.639: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.639: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.639: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.639: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.639: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.639: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.639: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.640: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.640: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.640: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.640: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.640: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.640: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.640: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.640: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.640: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.640: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.641: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.641: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.641: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.641: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.641: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.641: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.641: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.642: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.642: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.642: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.642: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.642: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.642: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.642: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.642: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.642: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.643: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.643: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.643: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.643: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.643: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.643: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.643: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.643: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.644: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.644: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.644: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.644: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.644: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.644: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.644: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.644: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.645: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.645: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.645: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.645: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.645: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.645: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.645: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.645: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.646: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.646: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.646: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.646: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.646: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.646: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.646: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.646: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.647: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.647: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.647: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.647: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.647: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.647: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.647: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.647: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.648: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.648: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.648: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.648: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.648: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.648: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.648: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.648: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.649: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.649: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.649: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.649: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.649: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.649: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.649: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.649: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.650: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.650: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.650: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.650: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.650: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.650: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.650: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.650: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.651: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.651: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.651: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.651: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.651: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.651: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.651: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.651: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.651: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.652: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.652: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.652: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.652: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.652: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.652: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.652: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.653: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.653: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.653: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.653: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.653: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.653: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.653: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.653: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.653: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.653: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.653: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.653: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.653: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.653: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.654: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.654: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.655: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.655: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.655: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.655: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.655: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.655: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.655: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.655: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.656: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.656: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.656: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.656: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.656: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.656: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.656: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.656: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.656: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.656: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.656: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.657: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.657: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.657: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.657: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.657: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.657: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.657: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.657: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.657: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.657: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.657: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.658: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.658: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.658: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.658: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.658: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.659: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.659: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.659: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.659: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.659: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.659: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.659: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.659: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.659: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.659: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.659: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.660: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.660: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.660: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.660: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.660: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.660: [vfs7552] CAPTURE_NUM_STATES entering state 2 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.660: [vfs7552] REQUEST CHUNK entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.660: Sending vfs7552_read_image_chunk 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.661: [vfs7552] REQUEST CHUNK completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.661: [vfs7552] CAPTURE_NUM_STATES entering state 3 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.661: [vfs7552] CAPTURE_NUM_STATES entering state 2 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.661: [vfs7552] REQUEST CHUNK entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.661: Sending vfs7552_read_image_chunk 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.662: [vfs7552] REQUEST CHUNK completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.662: [vfs7552] CAPTURE_NUM_STATES entering state 3 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.662: [vfs7552] CAPTURE_NUM_STATES entering state 2 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.662: [vfs7552] REQUEST CHUNK entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.662: Sending vfs7552_read_image_chunk 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.663: [vfs7552] REQUEST CHUNK completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.663: [vfs7552] CAPTURE_NUM_STATES entering state 3 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.663: [vfs7552] CAPTURE_NUM_STATES entering state 4 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.663: Cleaning image 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.663: variance_after = 1737 264s 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.663: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.663: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.663: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.664: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.664: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.664: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.664: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.664: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.664: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.664: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.664: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.665: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.665: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.665: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.665: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.665: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.665: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.665: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.665: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.666: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.666: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.666: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.666: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.666: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.666: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.666: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.666: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.667: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.667: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.667: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.667: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.667: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.667: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.667: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.667: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.668: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.668: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.668: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.668: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.668: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.668: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.668: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.668: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.668: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.668: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.669: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.669: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.669: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.669: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.669: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.669: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.670: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.670: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.670: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.670: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.670: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.670: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.670: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.670: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.670: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.670: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.671: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.671: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.671: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.671: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.671: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.671: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.671: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.671: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.672: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.672: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.672: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.672: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.672: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.672: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.672: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.672: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.673: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.673: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.673: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.673: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.673: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.673: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.673: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.673: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.674: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.674: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.674: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.674: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.674: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.674: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.674: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.674: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.675: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.675: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.675: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.675: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.675: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.675: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.675: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.675: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.676: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.676: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.676: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.676: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.676: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.676: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.676: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.676: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.677: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.677: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.677: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.677: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.677: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.677: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.677: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.677: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.678: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.678: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.678: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.678: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.678: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.678: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.678: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.678: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.678: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.678: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.678: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.678: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.678: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.678: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.679: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.679: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.679: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.679: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.679: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.679: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.679: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.679: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.680: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.680: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.680: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.680: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.680: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.680: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.680: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.680: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.681: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.681: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.681: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.681: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.681: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.681: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.681: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.681: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.682: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.682: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.682: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.682: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.682: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.682: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.682: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.682: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.683: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.683: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.683: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.683: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.683: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.683: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.683: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.683: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.683: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.683: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.684: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.684: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.684: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.684: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.684: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.684: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.684: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.684: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.685: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.685: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.685: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.685: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.685: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.685: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.685: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.685: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.686: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.686: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.686: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.686: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.686: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.686: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.686: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.686: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.687: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.687: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.687: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.687: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.687: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.687: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.687: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.687: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.688: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.688: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.688: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.688: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.688: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.688: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.688: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.688: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.689: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.689: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.689: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.689: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.689: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.689: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.689: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.689: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.690: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.690: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.690: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.690: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.690: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.690: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.690: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.690: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.691: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.691: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.691: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.691: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.691: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.691: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.691: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.691: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.692: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.692: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.692: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.692: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.692: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.692: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.692: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.692: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.693: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.693: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.693: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.693: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.693: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.693: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.693: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.693: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.694: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.694: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.694: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.694: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.694: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.694: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.694: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.694: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.695: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.695: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.695: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.695: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.695: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.695: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.695: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.695: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.696: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.696: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.696: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.696: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.696: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.696: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.696: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.696: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.697: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.697: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.697: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.697: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.697: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.697: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.697: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.697: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.697: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.697: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.697: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.697: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.697: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.697: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.698: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.698: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.698: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.698: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.698: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.698: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.698: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.698: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.699: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.699: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.699: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.699: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.699: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.700: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.700: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.700: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.700: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.700: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.700: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.700: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.700: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.700: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.700: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.700: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.701: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.701: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.701: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.701: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.701: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.701: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.701: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.701: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.702: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.702: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.702: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.702: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.702: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.702: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.702: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.702: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.703: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.703: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.703: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.703: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.703: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.703: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.703: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.703: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.704: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.704: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.704: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.704: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.704: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.704: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.704: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.704: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.705: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.705: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.705: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.705: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.705: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.705: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.705: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.705: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.706: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.706: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.706: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.706: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.706: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.706: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.706: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.706: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.707: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.707: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.707: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.707: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.707: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.707: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.707: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.707: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.708: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.708: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.708: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.708: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.708: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.708: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.708: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.708: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.708: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.709: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.709: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.709: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.709: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.709: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.709: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.709: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.709: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.709: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.710: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.710: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.710: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.710: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.710: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.710: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.710: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.710: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.711: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.711: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.711: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.711: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.711: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.711: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.711: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.711: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.712: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.712: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.712: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.712: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.712: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.712: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.712: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.712: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.713: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.713: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.713: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.713: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.713: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.713: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.713: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.713: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.714: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.714: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.714: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.714: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.714: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.714: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.714: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.714: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.715: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.715: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.715: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.715: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.715: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.715: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.715: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.715: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.716: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.716: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.716: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.716: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.716: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.716: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.716: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.716: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.717: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.717: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.717: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.717: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.717: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.717: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.717: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.717: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.718: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.718: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.718: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.718: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.718: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.718: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.718: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.718: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.719: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.719: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.719: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.719: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.719: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.719: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.719: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.719: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.720: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.720: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.720: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.720: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.720: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.720: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.720: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.720: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.721: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.721: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.721: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.721: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.721: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.721: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.721: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.721: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.722: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.722: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.722: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.722: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.722: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.722: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.722: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.722: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.723: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.723: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.723: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.723: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.723: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.723: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.723: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.723: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.723: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.723: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.723: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.723: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.723: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.723: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.724: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.724: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.724: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.724: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.724: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.724: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.724: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.724: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.725: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.725: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.725: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.725: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.725: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.725: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.725: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.725: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.726: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.726: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.726: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.726: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.726: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.726: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.726: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.726: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.727: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.727: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.727: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.727: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.727: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.727: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.727: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.727: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.728: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.728: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.728: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.728: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.728: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.728: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.728: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.728: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.729: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.729: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.729: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.729: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.729: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.729: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.729: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.729: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.730: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.730: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.730: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.730: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.730: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.730: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.730: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.730: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.730: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.731: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.731: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.731: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.731: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.731: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.731: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.731: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.731: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.731: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.732: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.732: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.732: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.732: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.732: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.732: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.732: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.732: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.733: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.733: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.733: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.733: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.733: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.733: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.733: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.733: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.734: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.734: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.734: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.734: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.734: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.734: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.734: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.734: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.735: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.735: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.735: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.735: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.735: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.735: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.735: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.735: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.736: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.736: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.736: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.736: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.736: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.736: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.736: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.736: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.737: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.737: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.737: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.737: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.737: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.737: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.737: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.737: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.738: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.738: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.738: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.738: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.738: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.738: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.738: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.738: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.739: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.739: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.739: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.739: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.739: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.739: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.739: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.739: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.740: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.740: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.740: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.740: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.740: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.740: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.740: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.740: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.740: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.741: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.741: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.741: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.741: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.741: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.741: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.741: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.741: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.742: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.742: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.742: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.742: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.742: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.742: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.742: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.742: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.742: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.742: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.742: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.742: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.742: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.743: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.743: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.743: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.743: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.743: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.743: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.743: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.743: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.744: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.744: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.744: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.744: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.744: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.744: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.744: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.744: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.745: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.745: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.745: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.745: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.745: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.745: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.745: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.745: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.746: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.746: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.746: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.746: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.746: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.746: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.746: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.746: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.747: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.747: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.747: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.747: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.747: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.747: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.747: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.747: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.748: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.748: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.748: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.748: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.748: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.748: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.748: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.748: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.748: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.749: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.749: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.749: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.749: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.749: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.749: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.749: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.750: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.750: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.750: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.750: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.750: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.750: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.750: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.750: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.750: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.751: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.751: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.751: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.751: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.751: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.752: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.752: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.752: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.752: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.752: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.752: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.752: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.752: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.753: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.753: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.753: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.753: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.753: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.753: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.753: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.753: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.753: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.753: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.754: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.754: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.754: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.754: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.754: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.754: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.754: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.754: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.755: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.755: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.755: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.755: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.755: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.755: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.755: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.755: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.756: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.756: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.756: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.756: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.756: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.756: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.756: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.756: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.757: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.757: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.757: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.757: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.757: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.757: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.757: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.757: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.758: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.758: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.758: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.758: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.758: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.758: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.758: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.758: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.759: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.759: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.759: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.759: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.759: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.759: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.759: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.759: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.760: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.760: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.760: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.760: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.760: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.760: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.760: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.760: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.761: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.761: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.761: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.761: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.761: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.761: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.761: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.761: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.762: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.762: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.762: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.762: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.762: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.762: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.762: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.762: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.762: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.763: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.763: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.763: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.763: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.763: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.763: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.763: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.764: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.764: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.764: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.764: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.764: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.764: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.764: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.764: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.765: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.765: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.765: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.765: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.765: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.765: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.765: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.765: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.766: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.766: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.766: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.766: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.766: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.766: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.766: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.766: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.766: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.766: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.766: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.766: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.766: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.766: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.767: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.767: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.767: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.767: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.767: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.767: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.767: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.767: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.768: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.768: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.768: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.768: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.768: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.768: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.768: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.768: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.769: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.769: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.769: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.769: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.769: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.769: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.769: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.769: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.770: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.770: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.770: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.770: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.770: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.770: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.770: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.770: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.771: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.771: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.771: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.771: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.771: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.771: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.771: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.771: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.772: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.772: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.772: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.772: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.772: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.772: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.773: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.773: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.773: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.773: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.773: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.773: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.773: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.773: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.774: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.774: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.774: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.774: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.774: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.774: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.774: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.774: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.775: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.775: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.775: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.775: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.775: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.775: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.775: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.775: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.775: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.775: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.776: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.776: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.776: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.776: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.776: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.776: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.776: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.777: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.777: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.777: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.777: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.777: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.777: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.777: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.777: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.778: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.778: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.778: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.778: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.778: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.778: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.778: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.778: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.779: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.779: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.779: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.779: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.779: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.779: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.779: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.779: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.780: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.780: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.780: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.780: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.780: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.780: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.780: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.780: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.781: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.781: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.781: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.781: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.781: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.781: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.781: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.781: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.782: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.782: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.782: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.782: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.782: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.782: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.782: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.782: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.783: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.783: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.783: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.783: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.783: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.783: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.783: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.783: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.783: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.784: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.784: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.784: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.784: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.784: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.784: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.784: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.784: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.784: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.784: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.784: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.785: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.785: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.786: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.786: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.786: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.786: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.786: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.786: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.786: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.786: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.786: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.786: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.786: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.786: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.786: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.786: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.787: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.787: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.787: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.787: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.787: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.787: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.787: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.787: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.788: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.788: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.788: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.788: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.788: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.788: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.788: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.788: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.789: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.789: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.789: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.789: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.789: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.789: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.789: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.789: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.790: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.790: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.790: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.790: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.790: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.790: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.790: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.790: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.791: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.791: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.792: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.792: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.792: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.792: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.792: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.792: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.792: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.792: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.792: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.792: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.792: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.792: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.792: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.792: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.793: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.793: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.793: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.793: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.793: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.793: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.793: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.793: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.794: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.794: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.794: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.794: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.794: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.794: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.794: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.794: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.795: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.795: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.795: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.795: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.795: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.795: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.795: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.795: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.796: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.796: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.796: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.796: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.796: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.796: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.796: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.797: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.797: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.797: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.797: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.797: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.797: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.797: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.797: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.797: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.797: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.798: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.798: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.798: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.798: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.798: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.798: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.798: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.798: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.799: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.799: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.799: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.799: [vfs7552] CAPTURE_NUM_STATES entering state 2 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.799: [vfs7552] REQUEST CHUNK entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.799: Sending vfs7552_read_image_chunk 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.799: [vfs7552] REQUEST CHUNK completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.799: [vfs7552] CAPTURE_NUM_STATES entering state 3 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.800: [vfs7552] CAPTURE_NUM_STATES entering state 2 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.800: [vfs7552] REQUEST CHUNK entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.800: Sending vfs7552_read_image_chunk 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.800: [vfs7552] REQUEST CHUNK completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.800: [vfs7552] CAPTURE_NUM_STATES entering state 3 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.801: [vfs7552] CAPTURE_NUM_STATES entering state 2 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.801: [vfs7552] REQUEST CHUNK entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.801: Sending vfs7552_read_image_chunk 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.801: [vfs7552] REQUEST CHUNK completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.801: [vfs7552] CAPTURE_NUM_STATES entering state 3 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.802: [vfs7552] CAPTURE_NUM_STATES entering state 4 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.802: Cleaning image 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.802: variance_after = 1526 264s 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.802: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.802: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.802: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.802: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.802: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.803: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.803: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.803: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.803: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.803: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.803: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.803: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.803: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.804: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.804: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.804: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.804: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.804: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.804: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.804: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.804: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.805: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.805: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.805: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.805: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.805: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.805: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.805: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.805: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.806: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.806: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.806: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.806: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.806: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.806: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.806: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.806: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.807: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.807: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.807: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.807: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.807: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.807: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.807: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.807: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.808: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.808: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.808: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.808: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.808: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.808: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.808: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.808: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.809: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.809: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.809: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.809: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.809: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.809: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.809: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.809: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.810: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.810: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.810: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.810: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.810: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.810: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.810: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.810: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.811: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.811: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.811: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.811: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.811: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.811: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.811: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.811: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.811: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.811: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.812: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.812: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.812: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.812: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.812: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.812: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.812: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.812: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.812: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.812: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.812: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.812: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.813: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.813: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.813: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.813: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.813: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.813: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.813: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.813: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.814: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.814: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.814: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.814: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.814: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.814: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.814: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.814: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.815: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.815: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.815: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.815: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.815: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.815: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.815: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.815: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.816: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.816: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.816: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.816: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.816: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.816: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.816: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.816: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.817: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.817: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.817: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.817: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.817: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.817: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.817: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.817: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.818: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.818: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.818: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.818: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.818: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.818: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.818: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.818: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.819: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.819: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.819: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.819: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.819: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.819: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.819: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.819: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.820: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.820: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.820: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.820: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.820: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.820: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.820: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.820: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.821: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.821: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.821: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.821: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.821: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.821: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.821: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.821: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.822: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.822: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.822: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.822: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.822: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.822: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.822: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.822: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.823: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.823: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.823: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.823: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.823: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.823: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.823: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.823: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.824: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.824: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.824: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.824: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.824: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.824: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.824: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.824: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.825: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.825: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.825: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.825: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.825: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.825: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.825: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.825: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.826: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.826: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.826: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.826: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.826: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.826: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.826: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.826: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.826: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.826: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.827: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.827: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.827: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.827: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.827: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.827: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.827: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.827: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.828: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.828: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.828: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.828: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.828: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.828: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.828: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.828: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.829: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.829: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.829: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.829: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.829: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.829: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.829: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.829: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.830: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.830: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.830: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.830: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.830: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.830: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.830: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.831: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.831: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.831: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.831: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.831: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.831: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.831: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.831: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.831: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.832: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.832: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.832: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.832: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.832: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.832: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.832: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.832: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.833: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.833: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.833: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.833: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.833: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.833: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.833: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.833: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.834: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.834: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.834: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.834: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.834: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.834: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.835: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.835: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.835: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.835: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.835: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.835: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.835: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.835: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.836: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.836: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.836: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.836: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.836: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.836: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.836: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.836: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.837: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.837: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.837: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.837: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.837: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.837: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.837: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.837: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.838: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.838: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.838: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.838: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.838: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.838: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.838: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.838: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.839: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.839: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.839: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.839: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.839: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.839: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.839: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.839: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.840: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.840: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.840: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.840: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.840: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.840: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.840: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.840: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.841: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.841: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.841: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.841: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.841: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.841: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.841: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.841: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.841: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.841: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.841: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.841: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.841: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.841: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.842: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.842: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.842: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.842: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.842: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.842: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.842: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.842: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.843: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.843: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.843: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.843: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.843: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.843: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.843: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.844: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.844: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.844: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.844: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.844: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.844: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.844: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.844: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.845: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.845: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.845: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.845: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.845: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.845: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.845: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.845: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.846: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.846: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.846: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.846: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.846: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.846: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.846: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.846: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.847: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.847: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.847: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.847: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.847: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.847: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.847: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.847: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.848: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.848: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.848: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.848: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.848: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.848: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.848: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.848: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.849: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.849: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.849: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.849: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.849: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.849: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.849: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.849: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.850: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.850: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.850: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.850: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.850: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.850: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.850: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.850: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.851: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.851: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.851: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.851: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.851: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.851: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.851: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.851: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.852: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.852: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.852: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.852: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.852: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.852: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.852: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.852: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.853: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.853: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.853: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.853: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.853: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.853: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.853: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.853: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.854: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.854: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.854: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.854: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.854: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.854: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.854: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.854: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.855: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.855: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.855: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.855: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.855: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.855: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.855: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.855: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.856: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.856: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.856: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.856: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.856: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.856: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.856: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.856: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.857: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.857: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.857: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.857: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.857: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.857: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.857: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.857: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.858: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.858: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.858: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.858: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.858: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.858: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.858: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.858: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.859: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.859: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.859: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.859: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.859: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.859: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.859: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.859: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.860: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.860: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.860: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.860: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.860: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.860: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.860: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.860: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.861: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.861: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.861: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.861: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.861: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.861: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.861: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.861: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.862: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.862: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.862: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.862: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.862: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.862: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.862: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.862: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.862: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.862: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.863: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.863: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.863: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.863: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.863: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.863: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.863: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.864: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.864: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.864: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.864: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.864: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.864: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.864: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.864: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.864: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.865: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.865: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.865: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.865: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.865: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.865: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.865: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.865: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.866: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.866: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.866: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.866: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.866: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.866: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.866: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.866: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.867: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.867: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.867: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.867: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.867: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.867: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.867: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.867: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.868: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.868: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.868: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.868: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.868: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.868: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.868: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.868: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.869: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.869: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.869: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.869: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.869: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.869: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.869: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.869: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.870: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.870: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.870: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.870: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.870: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.870: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.870: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.870: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.871: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.871: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.871: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.871: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.871: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.871: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.871: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.871: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.872: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.872: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.872: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.872: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.872: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.872: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.872: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.872: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.873: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.873: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.873: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.873: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.873: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.873: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.873: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.873: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.874: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.874: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.874: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.874: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.874: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.874: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.874: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.874: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.875: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.875: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.875: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.875: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.875: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.875: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.875: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.875: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.876: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.876: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.876: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.876: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.876: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.876: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.876: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.876: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.877: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.877: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.877: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.877: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.877: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.877: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.877: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.877: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.878: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.878: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.878: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.878: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.878: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.878: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.878: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.878: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.879: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.879: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.879: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.879: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.879: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.879: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.879: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.879: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.880: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.880: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.880: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.880: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.880: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.880: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.880: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.880: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.881: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.881: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.881: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.881: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.881: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.881: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.881: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.881: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.882: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.882: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.882: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.882: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.882: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.882: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.882: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.882: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.883: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.883: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.883: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.883: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.883: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.883: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.883: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.883: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.884: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.884: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.884: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.884: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.884: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.884: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.884: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.884: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.885: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.885: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.885: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.885: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.885: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.885: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.885: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.885: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.886: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.886: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.886: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.886: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.886: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.886: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.886: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.886: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.887: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.887: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.887: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.887: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.887: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.887: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.887: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.887: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.888: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.888: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.888: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.888: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.888: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.888: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.888: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.888: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.889: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.889: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.889: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.889: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.889: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.889: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.889: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.889: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.890: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.890: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.890: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.890: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.890: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.890: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.890: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.890: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.891: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.891: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.891: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.891: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.891: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.891: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.891: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.891: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.892: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.892: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.892: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.892: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.892: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.892: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.892: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.892: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.893: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.893: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.893: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.893: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.893: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.893: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.893: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.893: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.894: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.894: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.894: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.894: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.894: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.894: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.894: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.894: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.895: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.895: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.895: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.895: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.895: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.895: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.895: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.895: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.896: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.896: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.896: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.896: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.896: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.896: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.896: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.896: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.897: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.897: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.897: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.897: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.897: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.897: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.897: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.897: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.898: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.898: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.898: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.898: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.898: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.898: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.898: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.898: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.899: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.899: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.899: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.899: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.899: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.899: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.899: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.899: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.900: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.900: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.900: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.900: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.900: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.900: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.900: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.900: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.901: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.901: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.901: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.901: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.901: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.901: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.901: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.901: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.902: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.902: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.902: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.902: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.902: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.902: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.902: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.902: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.903: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.903: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.903: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.903: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.903: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.903: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.903: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.903: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.904: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.904: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.904: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.904: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.904: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.904: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.904: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.904: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.905: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.905: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.905: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.905: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.905: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.905: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.905: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.905: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.906: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.906: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.906: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.906: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.906: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.906: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.906: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.906: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.907: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.907: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.907: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.907: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.907: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.907: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.907: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.907: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.908: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.908: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.908: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.908: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.908: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.908: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.908: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.908: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.908: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.908: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.908: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.908: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.908: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.909: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.909: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.909: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.909: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.909: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.909: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.909: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.909: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.909: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.910: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.910: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.910: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.910: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.910: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.910: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.910: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.910: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.911: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.911: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.911: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.911: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.911: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.911: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.911: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.911: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.912: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.912: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.912: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.912: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.912: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.912: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.912: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.912: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.913: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.913: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.913: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.913: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.913: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.913: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.913: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.913: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.914: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.914: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.914: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.914: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.914: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.914: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.914: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.914: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.915: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.915: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.915: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.915: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.915: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.915: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.915: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.915: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.916: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.916: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.916: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.916: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.916: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.916: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.916: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.916: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.917: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.917: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.917: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.917: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.917: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.917: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.917: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.917: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.917: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.918: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.918: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.918: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.918: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.918: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.918: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.918: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.919: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.919: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.919: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.919: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.919: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.919: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.919: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.920: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.920: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.920: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.920: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.920: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.920: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.920: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.920: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.921: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.921: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.921: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.921: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.921: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.921: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.921: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.921: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.922: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.922: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.922: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.922: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.922: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.922: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.922: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.922: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.923: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.923: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.923: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.923: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.923: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.923: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.923: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.923: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.924: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.924: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.924: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.924: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.924: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.924: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.924: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.924: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.925: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.925: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.925: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.925: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.925: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.925: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.925: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.925: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.926: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.926: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.926: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.926: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.926: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.926: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.926: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.926: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.927: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.927: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.927: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.927: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.927: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.927: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.927: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.927: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.928: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.928: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.928: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.928: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.929: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.929: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.929: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.929: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.929: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.930: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.930: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.930: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.930: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.930: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.930: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.930: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.930: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.931: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.931: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.931: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.931: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.931: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.931: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.931: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.931: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.932: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.932: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.932: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.932: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.932: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.932: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.932: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.932: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.932: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.932: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.932: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.932: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.932: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.932: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.933: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.933: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.933: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.933: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.934: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.934: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.934: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.934: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.934: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.934: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.935: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.935: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.935: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.935: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.935: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.935: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.936: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.936: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.936: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.936: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.936: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.936: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.936: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.936: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.936: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.937: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.937: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.937: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.937: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.937: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.937: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.937: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.937: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.937: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.937: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.937: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.937: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.937: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.938: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.938: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.939: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.939: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.939: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.939: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.939: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.939: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.939: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.939: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.939: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.939: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.939: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.939: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.939: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.939: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.940: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.940: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.940: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.940: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.940: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.940: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.940: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.940: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.941: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.941: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.941: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.941: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.941: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.941: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.941: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.941: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.942: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.942: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.942: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.942: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.942: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.942: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.942: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.942: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.943: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.943: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.943: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.943: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.943: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.943: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.944: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.944: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.944: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.944: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.944: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.944: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.944: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.944: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.945: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.945: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.945: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.945: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.945: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.945: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.945: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.945: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.946: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.946: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.946: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.946: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.946: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.946: [vfs7552] CAPTURE_NUM_STATES entering state 2 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.946: [vfs7552] REQUEST CHUNK entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.946: Sending vfs7552_read_image_chunk 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.946: [vfs7552] REQUEST CHUNK completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.946: [vfs7552] CAPTURE_NUM_STATES entering state 3 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.947: [vfs7552] CAPTURE_NUM_STATES entering state 2 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.947: [vfs7552] REQUEST CHUNK entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.947: Sending vfs7552_read_image_chunk 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.948: [vfs7552] REQUEST CHUNK completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.948: [vfs7552] CAPTURE_NUM_STATES entering state 3 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.948: [vfs7552] CAPTURE_NUM_STATES entering state 2 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.948: [vfs7552] REQUEST CHUNK entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.948: Sending vfs7552_read_image_chunk 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.949: [vfs7552] REQUEST CHUNK completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.949: [vfs7552] CAPTURE_NUM_STATES entering state 3 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.949: [vfs7552] CAPTURE_NUM_STATES entering state 4 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.949: Cleaning image 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.949: variance_after = 1435 264s 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.949: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.949: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.950: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.950: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.950: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.950: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.950: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.950: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.950: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.950: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.950: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.951: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.951: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.951: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.951: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.951: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.951: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.951: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.952: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.952: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.952: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.952: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.952: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.952: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.952: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.952: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.953: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.953: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.953: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.953: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.953: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.953: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.953: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.953: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.953: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.954: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.954: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.954: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.954: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.954: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.954: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.954: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.954: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.954: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.955: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.955: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.955: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.955: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.955: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.955: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.955: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.955: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.956: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.956: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.956: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.956: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.956: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.956: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.956: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.956: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.957: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.957: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.957: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.957: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.957: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.957: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.957: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.957: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.958: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.958: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.958: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.958: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.958: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.958: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.958: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.958: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.959: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.959: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.959: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.959: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.959: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.959: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.959: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.959: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.960: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.960: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.960: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.960: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.960: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.960: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.960: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.960: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.961: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.961: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.961: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.961: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.961: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.961: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.961: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.961: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.962: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.962: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.962: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.962: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.962: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.962: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.962: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.962: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.963: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.963: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.963: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.963: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.963: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.963: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.963: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.963: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.964: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.964: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.964: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.964: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.964: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.964: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.964: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.964: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.965: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.965: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.965: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.965: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.965: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.965: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.965: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.965: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.966: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.966: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.966: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.966: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.966: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.966: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.966: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.966: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.967: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.967: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.967: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.967: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.967: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.967: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.967: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.967: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.968: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.968: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.968: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.968: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.968: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.968: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.968: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.968: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.969: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.969: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.969: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.969: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.969: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.969: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.969: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.969: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.970: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.970: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.970: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.970: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.970: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.970: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.970: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.970: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.971: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.971: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.971: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.971: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.971: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.971: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.971: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.971: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.972: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.972: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.972: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.972: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.972: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.972: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.972: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.972: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.973: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.973: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.973: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.973: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.973: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.973: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.973: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.973: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.974: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.974: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.974: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.974: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.974: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.974: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.974: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.974: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.975: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.975: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.975: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.975: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.975: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.975: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.975: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.975: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.976: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.976: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.976: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.976: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.976: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.976: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.976: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.976: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.977: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.977: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.977: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.977: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.977: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.977: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.977: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.978: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.978: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.978: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.978: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.978: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.978: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.978: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.978: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.979: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.979: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.979: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.979: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.979: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.979: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.979: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.979: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.980: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.980: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.980: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.980: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.980: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.980: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.980: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.980: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.980: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.980: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.980: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.980: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.980: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.980: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.981: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.981: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.981: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.981: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.981: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.981: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.981: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.981: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.982: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.982: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.982: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.982: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.982: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.982: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.982: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.982: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.983: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.983: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.983: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.983: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.983: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.984: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.984: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.984: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.984: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.984: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.985: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.985: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.985: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.985: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.985: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.985: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.985: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.986: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.986: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.986: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.986: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.986: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.986: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.986: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.986: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.987: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.987: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.987: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.987: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.987: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.987: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.987: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.987: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.988: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.988: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.988: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.988: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.988: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.988: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.988: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.988: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.989: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.989: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.989: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.989: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.989: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.989: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.989: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.989: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.989: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.989: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.989: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.989: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.989: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.989: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.990: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.990: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.990: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.990: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.990: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.991: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.991: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.991: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.991: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.991: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.991: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.992: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.992: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.992: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.992: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.992: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.992: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.992: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.993: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.993: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.993: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.993: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.993: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.993: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.993: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.993: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.994: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.994: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.994: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.994: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.994: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.994: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.994: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.994: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.995: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.995: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.995: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.995: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.995: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.995: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.995: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.995: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.996: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.996: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.996: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.996: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.996: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.996: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.996: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.996: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.997: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.997: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.997: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.997: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.997: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.997: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.997: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.997: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.998: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.998: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.998: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.998: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.998: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.998: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.998: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.998: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.999: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.999: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.999: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.999: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.999: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.999: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:20.999: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:20.999: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.000: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.000: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.000: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.000: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.000: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.000: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.000: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.000: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.001: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.001: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.001: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.001: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.001: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.001: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.001: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.001: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.002: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.002: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.002: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.002: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.002: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.002: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.002: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.002: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.003: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.003: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.003: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.003: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.003: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.003: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.003: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.003: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.004: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.004: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.004: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.004: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.004: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.004: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.004: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.004: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.005: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.005: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.005: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.005: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.005: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.005: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.005: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.005: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.006: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.006: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.006: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.006: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.006: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.006: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.006: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.006: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.007: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.007: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.007: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.007: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.007: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.007: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.007: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.007: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.008: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.008: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.008: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.008: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.008: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.008: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.008: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.008: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.009: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.009: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.009: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.009: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.009: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.009: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.009: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.009: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.010: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.010: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.010: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.010: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.010: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.010: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.010: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.010: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.011: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.011: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.011: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.011: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.011: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.011: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.011: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.011: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.012: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.012: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.012: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.012: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.012: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.012: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.012: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.012: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.013: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.013: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.013: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.013: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.013: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.013: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.013: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.013: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.014: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.014: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.014: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.014: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.014: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.014: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.014: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.014: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.015: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.015: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.015: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.015: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.015: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.015: Sending vfs7552_is_image_ready 264s Executing: libfprint-2/driver-vfs7552.test 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.016: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.016: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.016: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.016: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.016: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.016: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.016: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.017: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.017: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.017: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.017: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.017: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.018: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.018: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.018: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.018: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.018: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.018: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.019: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.019: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.019: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.019: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.019: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.019: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.019: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.019: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.020: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.020: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.020: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.020: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.020: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.020: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.020: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.020: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.021: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.021: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.021: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.021: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.021: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.021: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.021: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.021: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.022: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.022: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.022: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.022: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.022: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.022: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.022: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.022: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.022: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.022: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.022: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.022: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.022: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.022: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.023: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.023: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.023: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.023: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.023: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.023: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.023: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.023: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.024: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.024: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.024: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.024: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.024: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.024: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.024: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.024: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.025: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.025: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.025: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.025: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.025: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.025: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.025: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.025: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.026: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.026: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.026: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.026: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.026: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.026: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.026: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.026: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.027: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.027: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.027: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.027: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.027: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.027: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.027: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.027: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.028: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.028: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.028: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.028: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.028: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.028: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.028: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.029: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.029: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.029: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.029: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.029: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.029: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.029: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.029: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.030: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.030: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.030: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.030: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.030: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.030: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.030: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.030: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.031: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.031: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.031: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.031: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.031: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.031: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.031: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.031: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.032: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.032: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.032: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.032: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.032: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.032: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.032: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.032: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.033: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.033: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.033: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.033: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.033: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.033: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.033: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.033: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.034: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.034: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.034: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.034: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.034: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.034: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.034: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.034: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.035: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.035: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.035: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.035: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.035: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.035: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.035: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.035: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.036: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.036: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.036: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.036: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.036: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.036: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.036: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.036: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.037: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.037: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.038: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.038: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.038: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.038: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.038: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.038: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.038: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.038: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.039: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.039: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.039: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.039: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.039: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.039: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.039: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.039: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.040: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.040: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.040: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.040: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.040: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.040: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.040: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.040: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.041: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.041: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.041: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.041: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.041: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.041: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.041: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.041: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.041: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.041: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.041: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.041: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.041: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.041: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.042: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.042: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.042: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.043: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.043: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.043: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.043: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.043: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.043: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.043: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.044: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.044: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.044: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.044: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.044: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.044: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.044: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.044: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.045: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.045: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.045: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.045: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.045: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.045: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.045: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.045: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.045: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.045: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.045: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.045: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.045: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.045: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.046: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.046: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.046: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.046: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.047: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.047: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.047: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.047: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.047: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.047: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.047: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.048: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.048: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.048: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.048: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.048: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.048: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.048: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.048: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.048: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.048: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.048: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.048: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.048: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.049: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.049: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.049: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.049: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.049: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.049: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.049: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.049: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.050: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.050: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.050: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.051: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.051: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.051: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.051: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.051: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.051: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.051: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.052: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.052: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.052: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.052: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.052: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.052: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.052: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.052: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.053: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.053: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.053: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.053: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.053: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.053: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.053: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.053: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.054: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.054: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.054: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.054: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.054: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.054: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.054: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.054: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.055: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.055: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.055: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.055: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.055: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.055: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.055: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.055: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.056: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.056: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.056: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.056: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.056: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.056: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.057: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.057: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.057: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.057: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.057: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.057: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.057: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.057: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.057: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.057: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.058: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.058: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.058: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.058: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.058: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.058: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.058: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.058: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.059: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.059: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.059: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.059: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.059: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.059: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.059: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.059: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.060: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.060: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.060: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.060: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.060: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.060: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.060: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.060: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.061: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.061: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.061: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.061: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.061: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.061: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.061: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.061: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.062: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.062: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.062: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.062: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.062: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.062: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.062: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.062: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.063: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.063: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.063: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.063: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.063: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.063: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.063: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.063: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.064: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.064: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.064: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.064: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.064: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.064: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.064: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.064: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.065: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.065: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.065: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.065: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.065: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.065: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.065: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.065: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.066: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.066: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.066: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.066: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.067: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.067: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.067: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.067: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.067: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.067: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.067: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.067: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.068: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.068: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.068: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.068: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.068: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.068: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.068: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.068: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.069: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.069: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.069: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.069: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.069: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.069: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.069: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.069: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.070: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.070: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.070: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.070: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.070: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.070: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.070: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.070: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.071: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.071: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.071: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.071: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.071: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.071: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.071: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.071: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.072: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.072: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.072: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.072: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.072: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.072: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.072: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.072: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.073: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.073: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.073: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.073: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.073: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.073: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.073: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.074: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.074: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.074: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.074: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.075: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.075: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.075: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.075: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.075: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.075: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.075: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.076: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.076: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.076: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.076: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.076: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.076: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.076: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.076: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.077: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.077: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.077: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.077: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.077: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.077: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.077: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.077: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.078: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.078: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.078: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.078: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.078: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.078: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.079: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.079: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.079: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.079: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.079: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.079: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.079: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.079: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.080: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.080: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.080: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.080: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.080: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.080: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.080: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.080: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.081: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.081: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.081: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.081: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.081: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.081: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.081: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.081: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.081: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.081: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.082: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.082: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.082: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.082: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.082: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.082: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.083: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.083: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.083: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.083: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.083: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.083: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.083: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.083: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.084: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.084: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.084: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.084: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.084: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.084: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.084: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.084: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.085: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.085: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.085: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.085: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.085: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.085: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.085: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.085: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.086: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.086: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.086: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.086: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.086: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.086: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.086: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.086: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.087: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.087: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.087: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.087: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.087: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.087: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.087: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.087: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.088: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.088: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.088: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.088: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.088: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.088: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.088: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.088: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.089: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.089: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.089: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.089: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.089: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.089: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.089: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.089: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.090: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.090: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.090: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.090: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.090: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.090: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.090: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.090: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.091: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.091: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.091: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.091: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.091: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.091: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.091: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.091: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.092: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.092: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.092: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.092: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.092: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.092: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.092: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.092: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.093: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.093: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.093: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.093: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.093: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.094: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.094: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.094: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.094: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.095: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.095: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.095: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.095: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.095: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.095: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.095: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.095: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.096: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.096: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.096: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.096: [vfs7552] CAPTURE_NUM_STATES entering state 2 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.096: [vfs7552] REQUEST CHUNK entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.096: Sending vfs7552_read_image_chunk 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.096: [vfs7552] REQUEST CHUNK completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.096: [vfs7552] CAPTURE_NUM_STATES entering state 3 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.097: [vfs7552] CAPTURE_NUM_STATES entering state 2 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.097: [vfs7552] REQUEST CHUNK entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.097: Sending vfs7552_read_image_chunk 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.097: [vfs7552] REQUEST CHUNK completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.097: [vfs7552] CAPTURE_NUM_STATES entering state 3 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.098: [vfs7552] CAPTURE_NUM_STATES entering state 2 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.098: [vfs7552] REQUEST CHUNK entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.098: Sending vfs7552_read_image_chunk 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.098: [vfs7552] REQUEST CHUNK completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.098: [vfs7552] CAPTURE_NUM_STATES entering state 3 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.099: [vfs7552] CAPTURE_NUM_STATES entering state 4 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.099: Cleaning image 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.099: variance_after = 1425 264s 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.099: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.099: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.099: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.100: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.100: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.100: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.100: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.100: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.100: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.100: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.100: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.100: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.100: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.101: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.101: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.101: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.101: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.101: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.101: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.101: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.101: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.102: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.102: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.102: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.102: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.102: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.102: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.103: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.103: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.103: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.103: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.103: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.103: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.103: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.103: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.104: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.104: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.104: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.104: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.104: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.104: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.104: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.104: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.105: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.105: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.105: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.105: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.105: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.105: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.105: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.105: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.106: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.106: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.106: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.106: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.106: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.106: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.106: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.106: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.107: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.107: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.107: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.107: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.107: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.107: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.107: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.107: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.108: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.108: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.108: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.108: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.108: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.108: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.108: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.108: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.109: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.109: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.109: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.109: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.109: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.109: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.109: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.109: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.110: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.110: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.110: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.110: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.110: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.110: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.110: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.110: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.110: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.110: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.111: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.111: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.111: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.111: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.111: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.111: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.111: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.111: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.112: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.112: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.112: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.112: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.112: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.112: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.113: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.113: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.113: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.113: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.113: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.113: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.113: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.113: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.114: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.114: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.114: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.114: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.114: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.114: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.114: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.114: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.115: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.115: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.115: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.115: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.115: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.115: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.115: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.115: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.116: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.116: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.116: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.116: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.116: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.116: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.116: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.116: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.117: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.117: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.117: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.117: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.117: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.117: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.117: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.117: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.118: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.118: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.118: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.118: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.118: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.118: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.118: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.118: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.119: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.119: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.119: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.119: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.119: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.119: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.119: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.119: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.120: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.120: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.120: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.121: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.121: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.121: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.121: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.121: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.121: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.121: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.121: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.121: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.121: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.122: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.122: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.122: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.122: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.122: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.123: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.123: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.123: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.123: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.123: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.123: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.123: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.123: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.124: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.124: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.124: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.124: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.124: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.124: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.124: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.124: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.125: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.125: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.125: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.125: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.125: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.125: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.125: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.125: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.126: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.126: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.126: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.126: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.126: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.126: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.126: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.126: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.127: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.127: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.127: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.127: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.127: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.127: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.127: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.127: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.128: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.128: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.128: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.128: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.128: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.128: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.128: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.128: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.129: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.129: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.129: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.129: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.129: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.129: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.129: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.129: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.130: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.130: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.130: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.130: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.130: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.130: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.130: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.130: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.131: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.131: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.131: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.131: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.131: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.131: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.131: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.131: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.132: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.132: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.132: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.132: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.132: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.132: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.132: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.132: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.133: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.133: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.133: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.133: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.133: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.133: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.133: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.133: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.134: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.134: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.134: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.134: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.134: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.134: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.134: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.135: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.135: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.135: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.135: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.135: [vfs7552] CAPTURE_NUM_STATES entering state 0 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.135: [vfs7552] QUERY DATA READY entering state 0 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.135: Sending vfs7552_is_image_ready 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.135: [vfs7552] QUERY DATA READY entering state 1 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.135: Receiving 64 bytes 264s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.136: Got 6 bytes out of 64 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.136: [vfs7552] QUERY DATA READY completed successfully 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.136: [vfs7552] CAPTURE_NUM_STATES entering state 1 264s (process:1992): libfprint-SSM-DEBUG: 17:02:21.136: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.136: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.136: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.136: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.136: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.137: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.137: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.137: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.137: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.137: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.137: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.137: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.138: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.138: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.138: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.138: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.138: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.138: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.138: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.138: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.139: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.139: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.139: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.139: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.139: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.139: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.140: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.140: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.140: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.140: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.140: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.140: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.140: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.140: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.140: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.140: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.141: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.141: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.141: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.141: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.142: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.142: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.142: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.142: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.142: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.142: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.142: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.142: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.143: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.143: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.143: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.143: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.143: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.143: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.143: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.144: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.144: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.144: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.144: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.144: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.144: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.144: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.144: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.145: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.145: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.145: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.145: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.145: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.145: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.146: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.146: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.146: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.146: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.146: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.146: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.146: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.146: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.147: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.147: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.147: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.147: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.147: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.148: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.148: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.148: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.148: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.148: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.149: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.149: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.149: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.149: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.149: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.149: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.150: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.150: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.150: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.150: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.150: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.150: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.150: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.150: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.151: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.151: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.151: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.151: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.151: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.151: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.152: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.152: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.152: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.152: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.152: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.152: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.152: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.153: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.153: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.153: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.153: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.153: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.153: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.154: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.154: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.154: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.154: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.154: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.154: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.154: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.154: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.155: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.155: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.155: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.155: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.155: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.155: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.156: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.156: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.156: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.156: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.156: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.156: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.156: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.156: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.157: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.157: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.157: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.157: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.157: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.157: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.158: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.158: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.158: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.158: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.158: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.158: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.158: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.159: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.159: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.159: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.159: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.159: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.160: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.160: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.160: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.160: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.160: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.160: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.161: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.161: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.161: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.161: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.161: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.161: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.161: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.161: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.162: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.162: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.162: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.162: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.162: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.162: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.162: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.163: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.163: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.163: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.163: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.163: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.163: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.163: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.163: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.164: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.164: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.165: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.165: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.165: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.165: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.165: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.165: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.165: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.165: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.166: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.166: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.166: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.166: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.166: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.166: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.166: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.166: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.167: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.167: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.167: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.167: [vfs7552] CAPTURE_NUM_STATES entering state 2 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.167: [vfs7552] REQUEST CHUNK entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.167: Sending vfs7552_read_image_chunk 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.167: [vfs7552] REQUEST CHUNK completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.167: [vfs7552] CAPTURE_NUM_STATES entering state 3 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.168: [vfs7552] CAPTURE_NUM_STATES entering state 2 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.168: [vfs7552] REQUEST CHUNK entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.168: Sending vfs7552_read_image_chunk 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.168: [vfs7552] REQUEST CHUNK completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.168: [vfs7552] CAPTURE_NUM_STATES entering state 3 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.169: [vfs7552] CAPTURE_NUM_STATES entering state 2 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.169: [vfs7552] REQUEST CHUNK entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.169: Sending vfs7552_read_image_chunk 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.169: [vfs7552] REQUEST CHUNK completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.169: [vfs7552] CAPTURE_NUM_STATES entering state 3 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.170: [vfs7552] CAPTURE_NUM_STATES entering state 4 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.170: Cleaning image 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.170: variance_after = 1532 265s 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.170: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.170: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.170: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.170: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.171: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.171: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.171: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.171: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.171: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.171: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.172: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.172: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.172: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.172: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.172: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.172: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.172: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.172: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.173: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.173: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.173: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.173: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.173: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.173: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.173: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.173: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.174: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.174: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.174: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.174: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.174: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.174: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.174: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.174: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.175: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.175: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.175: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.175: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.175: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.175: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.175: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.175: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.176: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.176: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.176: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.176: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.176: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.176: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.176: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.177: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.177: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.177: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.177: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.177: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.177: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.177: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.177: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.178: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.178: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.178: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.178: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.178: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.178: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.179: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.179: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.179: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.179: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.179: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.179: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.180: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.180: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.180: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.180: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.180: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.180: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.180: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.181: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.181: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.181: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.181: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.181: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.181: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.181: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.182: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.182: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.182: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.182: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.182: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.182: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.182: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.182: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.183: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.183: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.183: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.183: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.183: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.183: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.184: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.184: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.184: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.184: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.184: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.184: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.184: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.184: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.185: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.185: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.185: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.185: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.185: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.185: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.185: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.185: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.186: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.186: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.186: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.186: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.186: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.186: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.186: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.187: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.187: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.187: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.187: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.187: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.187: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.187: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.187: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.188: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.188: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.188: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.188: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.188: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.188: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.189: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.189: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.189: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.189: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.189: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.189: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.189: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.189: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.190: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.190: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.190: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.190: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.190: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.190: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.190: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.190: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.191: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.191: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.191: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.191: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.191: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.191: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.191: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.191: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.192: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.192: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.192: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.192: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.192: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.192: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.192: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.192: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.193: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.193: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.193: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.193: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.193: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.193: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.194: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.194: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.194: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.194: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.194: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.194: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.194: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.194: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.195: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.195: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.195: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.195: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.195: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.195: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.195: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.196: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.196: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.196: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.196: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.197: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.197: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.197: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.197: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.197: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.197: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.197: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.197: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.197: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.197: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.197: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.197: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.198: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.198: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.198: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.198: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.198: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.198: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.198: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.198: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.199: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.199: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.200: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.200: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.200: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.200: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.200: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.200: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.200: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.200: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.201: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.201: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.201: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.201: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.201: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.201: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.201: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.201: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.202: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.202: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.202: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.202: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.202: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.202: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.203: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.203: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.203: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.203: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.203: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.203: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.204: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.204: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.204: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.204: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.204: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.204: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.204: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.204: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.205: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.205: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.205: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.205: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.205: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.205: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.206: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.206: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.206: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.206: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.206: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.206: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.206: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.206: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.207: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.207: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.207: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.207: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.207: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.207: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.208: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.208: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.208: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.208: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.208: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.208: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.208: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.208: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.209: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.209: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.209: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.209: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.209: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.209: [vfs7552] CAPTURE_NUM_STATES entering state 2 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.209: [vfs7552] REQUEST CHUNK entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.209: Sending vfs7552_read_image_chunk 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.210: [vfs7552] REQUEST CHUNK completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.210: [vfs7552] CAPTURE_NUM_STATES entering state 3 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.210: [vfs7552] CAPTURE_NUM_STATES entering state 2 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.210: [vfs7552] REQUEST CHUNK entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.210: Sending vfs7552_read_image_chunk 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.211: [vfs7552] REQUEST CHUNK completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.211: [vfs7552] CAPTURE_NUM_STATES entering state 3 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.211: [vfs7552] CAPTURE_NUM_STATES entering state 2 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.211: [vfs7552] REQUEST CHUNK entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.211: Sending vfs7552_read_image_chunk 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.212: [vfs7552] REQUEST CHUNK completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.212: [vfs7552] CAPTURE_NUM_STATES entering state 3 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.212: [vfs7552] CAPTURE_NUM_STATES entering state 4 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.212: Cleaning image 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.213: variance_after = 1691 265s 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.213: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.213: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.213: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.213: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.213: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.214: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.214: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.214: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.214: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.214: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.214: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.214: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.215: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.215: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.215: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.215: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.215: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.215: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.215: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.215: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.216: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.216: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.216: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.216: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.216: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.216: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.217: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.217: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.217: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.217: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.217: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.217: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.217: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.217: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.218: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.218: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.218: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.218: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.218: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.218: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.218: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.218: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.219: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.219: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.219: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.219: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.219: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.219: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.219: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.220: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.220: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.220: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.220: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.220: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.220: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.221: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.221: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.221: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.221: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.221: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.221: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.221: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.222: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.222: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.222: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.222: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.222: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.222: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.222: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.222: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.223: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.223: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.223: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.223: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.223: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.223: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.224: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.224: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.224: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.224: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.224: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.224: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.224: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.224: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.225: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.225: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.225: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.225: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.225: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.225: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.225: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.225: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.226: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.226: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.226: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.226: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.226: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.226: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.226: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.227: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.227: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.227: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.227: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.227: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.227: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.227: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.227: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.228: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.228: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.228: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.228: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.228: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.228: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.229: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.229: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.229: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.230: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.230: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.230: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.230: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.230: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.230: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.230: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.231: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.231: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.231: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.231: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.231: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.231: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.231: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.231: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.232: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.232: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.232: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.232: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.232: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.232: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.232: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.232: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.233: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.233: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.233: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.233: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.233: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.233: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.234: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.234: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.234: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.234: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.234: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.234: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.234: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.234: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.235: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.235: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.235: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.235: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.235: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.235: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.235: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.235: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.236: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.236: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.236: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.236: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.236: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.236: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.237: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.237: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.237: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.237: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.237: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.237: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.237: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.237: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.238: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.238: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.238: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.238: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.238: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.238: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.238: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.239: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.239: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.239: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.239: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.239: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.239: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.239: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.240: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.240: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.240: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.240: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.240: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.240: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.240: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.240: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.241: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.241: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.241: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.241: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.241: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.241: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.241: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.241: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.242: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.242: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.242: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.242: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.242: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.242: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.242: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.242: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.243: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.243: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.243: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.243: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.243: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.243: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.243: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.243: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.244: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.244: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.244: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.244: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.244: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.244: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.244: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.244: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.245: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.245: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.245: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.245: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.245: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.245: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.245: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.245: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.246: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.246: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.246: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.246: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.246: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.246: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.246: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.246: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.247: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.247: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.247: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.247: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.247: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.248: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.248: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.248: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.248: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.248: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.248: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.248: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.248: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.249: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.249: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.249: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.249: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.249: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.249: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.249: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.249: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.250: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.250: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.250: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.250: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.250: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.250: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.251: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.251: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.251: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.251: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.251: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.252: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.252: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.252: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.252: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.252: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.252: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.252: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.253: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.253: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.253: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.253: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.253: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.253: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.253: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.253: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.254: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.254: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.254: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.254: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.254: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.254: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.254: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.254: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.255: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.255: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.255: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.255: [vfs7552] CAPTURE_NUM_STATES entering state 2 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.255: [vfs7552] REQUEST CHUNK entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.255: Sending vfs7552_read_image_chunk 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.255: [vfs7552] REQUEST CHUNK completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.255: [vfs7552] CAPTURE_NUM_STATES entering state 3 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.256: [vfs7552] CAPTURE_NUM_STATES entering state 2 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.256: [vfs7552] REQUEST CHUNK entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.256: Sending vfs7552_read_image_chunk 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.256: [vfs7552] REQUEST CHUNK completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.256: [vfs7552] CAPTURE_NUM_STATES entering state 3 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.257: [vfs7552] CAPTURE_NUM_STATES entering state 2 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.257: [vfs7552] REQUEST CHUNK entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.257: Sending vfs7552_read_image_chunk 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.257: [vfs7552] REQUEST CHUNK completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.257: [vfs7552] CAPTURE_NUM_STATES entering state 3 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.258: [vfs7552] CAPTURE_NUM_STATES entering state 4 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.258: Cleaning image 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.258: variance_after = 1845 265s 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.258: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.258: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.258: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.258: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.258: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.259: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.259: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.259: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.259: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.259: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.259: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.259: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.259: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.260: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.260: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.260: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.260: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.260: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.260: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.260: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.260: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.261: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.261: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.261: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.261: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.261: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.261: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.261: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.261: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.262: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.262: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.262: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.262: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.262: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.262: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.262: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.262: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.263: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.263: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.263: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.263: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.263: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.263: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.264: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.264: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.264: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.264: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.264: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.264: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.264: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.264: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.265: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.265: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.265: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.265: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.265: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.265: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.265: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.265: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.266: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.266: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.266: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.266: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.266: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.266: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.266: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.266: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.267: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.267: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.267: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.267: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.267: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.267: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.267: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.267: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.268: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.268: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.268: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.268: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.268: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.268: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.268: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.268: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.269: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.269: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.269: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.269: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.269: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.269: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.269: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.269: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.270: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.270: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.270: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.270: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.270: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.270: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.270: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.270: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.271: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.271: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.271: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.271: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.271: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.271: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.271: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.271: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.272: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.272: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.272: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.273: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.273: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.273: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.273: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.273: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.273: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.273: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.274: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.274: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.274: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.274: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.274: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.274: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.274: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.274: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.275: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.275: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.275: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.275: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.275: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.275: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.275: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.275: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.276: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.276: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.276: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.276: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.276: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.276: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.277: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.277: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.277: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.277: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.277: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.277: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.277: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.277: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.278: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.278: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.278: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.278: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.278: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.278: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.278: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.278: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.279: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.279: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.279: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.279: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.279: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.279: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.279: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.279: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.280: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.280: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.280: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.280: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.280: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.280: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.280: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.280: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.281: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.281: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.281: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.281: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.281: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.281: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.281: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.281: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.282: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.282: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.282: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.282: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.282: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.282: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.282: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.282: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.283: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.283: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.283: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.283: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.283: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.283: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.283: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.283: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.284: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.284: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.284: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.284: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.284: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.284: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.284: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.284: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.285: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.285: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.285: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.286: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.286: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.286: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.286: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.286: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.286: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.286: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.286: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.286: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.287: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.287: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.287: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.287: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.287: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.287: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.288: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.288: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.288: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.288: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.288: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.288: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.288: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.289: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.289: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.289: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.289: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.289: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.289: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.289: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.289: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.290: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.290: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.290: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.290: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.290: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.290: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.290: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.291: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.291: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.291: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.291: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.291: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.291: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.291: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.291: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.292: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.292: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.292: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.292: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.292: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.292: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.292: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.292: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.292: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.292: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.293: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.293: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.293: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.293: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.293: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.293: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.294: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.294: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.294: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.294: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.294: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.294: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.294: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.294: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.295: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.295: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.295: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.295: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.295: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.295: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.295: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.295: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.296: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.296: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.296: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.296: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.296: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.296: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.296: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.296: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.297: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.297: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.297: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.297: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.297: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.297: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.297: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.297: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.298: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.298: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.298: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.298: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.299: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.299: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.299: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.299: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.299: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.299: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.299: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.299: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.299: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.299: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.299: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.300: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.300: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.300: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.300: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.300: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.300: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.300: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.301: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.301: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.301: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.301: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.301: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.301: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.301: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.301: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.301: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.301: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.302: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.302: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.302: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.302: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.302: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.303: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.303: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.303: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.303: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.303: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.304: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.304: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.304: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.304: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.304: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.304: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.304: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.304: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.305: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.305: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.305: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.305: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.305: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.305: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.306: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.306: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.306: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.306: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.306: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.306: [vfs7552] CAPTURE_NUM_STATES entering state 2 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.306: [vfs7552] REQUEST CHUNK entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.306: Sending vfs7552_read_image_chunk 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.307: [vfs7552] REQUEST CHUNK completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.307: [vfs7552] CAPTURE_NUM_STATES entering state 3 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.307: [vfs7552] CAPTURE_NUM_STATES entering state 2 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.307: [vfs7552] REQUEST CHUNK entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.307: Sending vfs7552_read_image_chunk 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.308: [vfs7552] REQUEST CHUNK completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.308: [vfs7552] CAPTURE_NUM_STATES entering state 3 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.308: [vfs7552] CAPTURE_NUM_STATES entering state 2 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.308: [vfs7552] REQUEST CHUNK entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.308: Sending vfs7552_read_image_chunk 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.309: [vfs7552] REQUEST CHUNK completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.309: [vfs7552] CAPTURE_NUM_STATES entering state 3 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.309: [vfs7552] CAPTURE_NUM_STATES entering state 4 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.309: Cleaning image 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.309: variance_after = 2342 265s 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.309: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.309: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.309: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.310: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.310: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.311: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.311: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.311: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.311: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.311: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.311: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.311: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.311: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.312: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.312: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.312: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.312: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.312: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.312: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.312: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.312: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.313: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.313: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.313: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.313: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.313: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.313: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.313: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.313: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.314: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.314: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.314: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.314: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.314: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.314: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.314: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.314: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.315: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.315: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.315: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.315: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.315: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.315: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.315: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.316: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.316: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.316: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.316: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.316: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.316: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.316: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.316: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.317: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.317: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.317: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.317: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.317: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.317: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.317: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.318: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.318: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.318: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.318: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.318: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.318: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.318: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.318: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.319: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.319: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.319: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.319: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.319: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.319: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.319: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.319: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.320: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.320: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.320: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.320: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.320: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.320: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.320: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.320: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.321: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.321: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.321: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.321: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.321: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.321: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.321: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.321: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.322: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.322: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.322: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.322: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.322: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.322: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.322: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.322: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.323: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.323: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.324: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.324: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.324: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.324: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.324: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.324: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.324: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.324: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.325: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.325: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.325: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.325: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.325: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.325: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.325: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.325: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.326: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.326: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.326: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.326: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.326: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.326: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.326: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.326: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.327: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.327: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.327: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.327: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.327: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.327: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.327: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.327: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.328: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.328: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.328: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.328: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.328: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.328: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.328: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.328: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.329: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.329: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.329: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.329: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.329: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.329: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.329: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.329: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.330: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.330: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.330: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.330: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.330: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.330: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.330: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.330: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.331: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.331: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.331: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.331: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.331: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.331: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.331: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-v/usr/libexec/installed-tests/libfprint-2/virtual-device.py:463: DeprecationWarning: FPrint.Device.supports_identify is deprecated 265s self.assertFalse(self.dev.supports_identify()) 265s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:464: DeprecationWarning: FPrint.Device.supports_capture is deprecated 265s self.assertFalse(self.dev.supports_capture()) 265s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:465: DeprecationWarning: FPrint.Device.has_storage is deprecated 265s self.assertFalse(self.dev.has_storage()) 265s fs7552-DEBUG: 17:02:21.331: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.332: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.332: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.332: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.332: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.332: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.332: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.332: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.332: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.333: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.333: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.333: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.333: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.333: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.333: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.333: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.333: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.334: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.334: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.334: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.334: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.334: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.334: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.334: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.334: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.335: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.335: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.335: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.335: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.335: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.335: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.335: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.336: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.336: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.336: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.336: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.336: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.336: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.336: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.336: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.336: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.337: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.337: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.337: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.337: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.337: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.337: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.337: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.337: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.338: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.338: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.338: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.338: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.338: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.338: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.338: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.338: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.339: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.339: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.339: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.339: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.339: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.339: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.339: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.339: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.340: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.340: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.340: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.340: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.340: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.340: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.340: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.340: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.341: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.341: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.341: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.341: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.341: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.341: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.341: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.341: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.342: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.342: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.342: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.342: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.342: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.342: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.343: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.343: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.343: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.343: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.343: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.343: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.343: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.343: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.344: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.344: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.344: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.344: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.344: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.344: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.344: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.344: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.345: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.345: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.345: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.345: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.345: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.345: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.345: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.345: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.346: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.346: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.346: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.346: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.346: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.346: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.346: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.346: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.347: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.347: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.347: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.348: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.348: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.348: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.348: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.348: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.348: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.348: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.349: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.349: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.349: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.349: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.349: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.349: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.349: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.349: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.350: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.350: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.350: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.350: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.350: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.350: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.350: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.350: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.351: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.351: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.351: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.351: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.351: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.351: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.351: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.351: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.352: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.352: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.352: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.352: [vfs7552] CAPTURE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.352: [vfs7552] QUERY DATA READY entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.352: Sending vfs7552_is_image_ready 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.353: [vfs7552] QUERY DATA READY entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.353: Receiving 64 bytes 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.353: Got 6 bytes out of 64 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.353: [vfs7552] QUERY DATA READY completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.353: [vfs7552] CAPTURE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.353: [vfs7552] CAPTURE_NUM_STATES entering state 2 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.353: [vfs7552] REQUEST CHUNK entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.353: Sending vfs7552_read_image_chunk 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.354: [vfs7552] REQUEST CHUNK completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.354: [vfs7552] CAPTURE_NUM_STATES entering state 3 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.354: [vfs7552] CAPTURE_NUM_STATES entering state 2 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.354: [vfs7552] REQUEST CHUNK entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.354: Sending vfs7552_read_image_chunk 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.355: [vfs7552] REQUEST CHUNK completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.355: [vfs7552] CAPTURE_NUM_STATES entering state 3 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.355: [vfs7552] CAPTURE_NUM_STATES entering state 2 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.356: [vfs7552] REQUEST CHUNK entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.356: Sending vfs7552_read_image_chunk 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.356: [vfs7552] REQUEST CHUNK completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.356: [vfs7552] CAPTURE_NUM_STATES entering state 3 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.356: [vfs7552] CAPTURE_NUM_STATES entering state 4 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.356: Cleaning image 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.357: variance_after = 16 265s 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.357: [vfs7552] CAPTURE_NUM_STATES completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.357: [vfs7552] DEACTIVATE_NUM_STATES entering state 0 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.367: [vfs7552] DEACTIVATE_NUM_STATES entering state 1 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.367: [vfs7552] STOP CAPTURE entering state 0 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.367: Sending vfs7552_cmd_04 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.367: [vfs7552] STOP CAPTURE entering state 1 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.367: Receiving 64 bytes 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.368: [vfs7552] STOP CAPTURE entering state 2 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.368: Sending vfs7552_cmd_52 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.368: [vfs7552] STOP CAPTURE entering state 3 265s (process:1992): libfprint-vfs7552-DEBUG: 17:02:21.368: Receiving 64 bytes 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.369: [vfs7552] STOP CAPTURE completed successfully 265s (process:1992): libfprint-SSM-DEBUG: 17:02:21.369: [vfs7552] DEACTIVATE_NUM_STATES completed successfully 265s (process:1992): libfprint-device-DEBUG: 17:02:21.369: Device reported finger status change: FP_FINGER_STATUS_NONE 265s (process:1992): libfprint-image_device-DEBUG: 17:02:21.369: Image device reported finger status: off 265s (process:1992): libfprint-image_device-DEBUG: 17:02:21.369: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 265s (process:1992): libfprint-image_device-DEBUG: 17:02:21.369: Deactivating image device 265s (process:1992): libfprint-image_device-DEBUG: 17:02:21.369: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 265s (process:1992): libfprint-image_device-DEBUG: 17:02:21.369: Image device deactivation completed 265s (process:1992): libfprint-image_device-DEBUG: 17:02:21.369: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 265s (process:1992): libfprint-device-DEBUG: 17:02:21.369: Device reported capture completion 265s (process:1992): libfprint-device-DEBUG: 17:02:21.369: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 265s (process:1992): libfprint-device-DEBUG: 17:02:21.369: Updated temperature model after 2.28 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 265s (process:1992): libfprint-image_device-DEBUG: 17:02:21.369: Image device close completed 265s (process:1992): libfprint-device-DEBUG: 17:02:21.369: Device reported close completion 265s (process:1992): libfprint-device-DEBUG: 17:02:21.370: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 265s (process:1992): libfprint-device-DEBUG: 17:02:21.370: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 265s ** (umockdev-run:1988): DEBUG: 17:02:21.444: umockdev.vala:150: Removing test bed /tmp/umockdev.R8G5J2 265s (umockdev-run:1988): GLib-DEBUG: 17:02:21.448: unsetenv() is not thread-safe and should not be used after threads are created 265s Comparing PNGs /tmp/libfprint-umockdev-test-7o_w9_dl/capture.png and /usr/share/installed-tests/libfprint-2/vfs7552/capture.png 265s PASS: libfprint-2/driver-vfs7552.test 265s Running test: libfprint-2/virtual-device.test 265s (process:1999): libfprint-context-DEBUG: 17:02:21.553: Initializing FpContext (libfprint version 1.94.7+tod1) 265s (process:1999): libfprint-tod-DEBUG: 17:02:21.553: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 265s (process:1999): libfprint-context-DEBUG: 17:02:21.554: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-hmegcyow/virtual-device.socket 265s (process:1999): libfprint-context-DEBUG: 17:02:21.555: created 265s (process:1999): libfprint-device-DEBUG: 17:02:21.555: Device reported probe completion 265s (process:1999): libfprint-device-DEBUG: 17:02:21.555: Completing action FPI_DEVICE_ACTION_PROBE in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:21.555: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s test_capture_unsupported (__main__.VirtualDevice.test_capture_unsupported) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.556: 97541085: ../libfprint/drivers/virtual-device.c:387 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:21.556: 97541143: ../libfprint/drivers/virtual-device-listener.c:153 265s (process:1999): libfprint-device-DEBUG: 17:02:21.556: Device reported open completion 265s (process:1999): libfprint-device-DEBUG: 17:02:21.556: Completing action FPI_DEVICE_ACTION_OPEN in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:21.556: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:21.557: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.557: Got instructions of length 16 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.557: Received command SET_KEEP_ALIVE 0 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.557: Keep alive toggled: 0 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:21.557: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.557: Got instructions of length 19 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.557: Received command SET_ENROLL_STAGES 5 265s (process:1999): libfprint-device-DEBUG: 17:02:21.557: Device reported close completion 265s (process:1999): libfprint-device-DEBUG: 17:02:21.557: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:21.557: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s ok 265s test_change_enroll_stages (__main__.VirtualDevice.test_change_enroll_stages) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.557: 97542480: ../libfprint/drivers/virtual-device.c:387 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:21.557: 97542487: ../libfprint/drivers/virtual-device-listener.c:153 265s (process:1999): libfprint-device-DEBUG: 17:02:21.557: Device reported open completion 265s (process:1999): libfprint-device-DEBUG: 17:02:21.557: Completing action FPI_DEVICE_ACTION_OPEN in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:21.557: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:21.557: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.557: Got instructions of length 20 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.557: Received command SET_ENROLL_STAGES 20 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:21.557: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.557: Got instructions of length 19 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.557: Received command SET_ENROLL_STAGES 1 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:21.558: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.558: Got instructions of length 19 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.558: Received command SET_ENROLL_STAGES 0 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:21.559: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.559: Got instructions of length 16 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.559: Received command SET_KEEP_ALIVE 0 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.559: Keep alive toggled: 0 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:21.560: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.560: Got instructions of length 19 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.560: Received command SET_ENROLL_STAGES 5 265s (process:1999): libfprint-device-DEBUG: 17:02:21.560: Device reported close completion 265s (process:1999): libfprint-device-DEBUG: 17:02:21.560: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:21.560: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s ok 265s test_change_scan_type (__main__.VirtualDevice.test_change_scan_type) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.560: 97545577: ../libfprint/drivers/virtual-device.c:387 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:21.560: 97545612: ../libfprint/drivers/virtual-device-listener.c:153 265s (process:1999): libfprint-device-DEBUG: 17:02:21.560: Device reported open completion 265s (process:1999): libfprint-device-DEBUG: 17:02:21.560: Completing action FPI_DEVICE_ACTION_OPEN in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:21.561: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:21.561: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.561: Got instructions of length 19 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.561: Received command SET_SCAN_TYPE press 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:21.561: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.561: Got instructions of length 19 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.561: Received command SET_SCAN_TYPE swipe 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:21.562: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.562: Got instructions of length 25 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.562: Received command SET_SCAN_TYPE eye-contact 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:21.562: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.562: Got instructions of length 16 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.562: Received command SET_KEEP_ALIVE 0 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.562: Keep alive toggled: 0 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:21.562: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.562: Got instructions of length 19 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.562: Received command SET_ENROLL_STAGES 5 265s (process:1999): libfprint-device-DEBUG: 17:02:21.562: Device reported close completion 265s (process:1999): libfprint-device-DEBUG: 17:02:21.562: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:21.562: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s ok 265s test_close_error (__main__.VirtualDevice.test_close_error) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.562: 97547901: ../libfprint/drivers/virtual-device.c:387 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:21.563: 97547908: ../libfprint/drivers/virtual-device-listener.c:153 265s (process:1999): libfprint-device-DEBUG: 17:02:21.563: Device reported open completion 265s (process:1999): libfprint-device-DEBUG: 17:02:21.563: Completing action FPI_DEVICE_ACTION_OPEN in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:21.563: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:21.563: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.563: Got instructions of length 9 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.563: Received command SLEEP 100 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:21.563: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.563: Got instructions of length 7 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.563: Received command ERROR 4 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.564: Processing command SLEEP 100 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.564: Sleeping 100ms 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.664: Sleeping completed 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.664: Processing command ERROR 4 265s (process:1999): libfprint-device-DEBUG: 17:02:21.664: Device reported close completion 265s (process:1999): libfprint-device-DEBUG: 17:02:21.664: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:21.664: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s ok 265s test_close_while_opening (__main__.VirtualDevice.test_close_while_opening) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.664: 97649735: ../libfprint/drivers/virtual-device.c:387 265s (process:1999): libfprint-device-DEBUG: 17:02:21.664: Device reported open completion 265s (process:1999): libfprint-device-DEBUG: 17:02:21.664: Completing action FPI_DEVICE_ACTION_OPEN in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:21.664: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:21.665: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.665: Got instructions of length 16 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.665: Received command SET_KEEP_ALIVE 1 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.665: Keep alive toggled: 1 265s (process:1999): libfprint-device-DEBUG: 17:02:21.665: Device reported close completion 265s (process:1999): libfprint-device-DEBUG: 17:02:21.665: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:21.665: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:21.665: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.665: Got instructions of length 9 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.665: Received command SLEEP 500 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.665: 97650196: ../libfprint/drivers/virtual-device.c:387 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.665: Processing command SLEEP 500 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:21.665: Sleeping 500ms 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.166: Sleeping completed 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.166: 98151107: ../libfprint/drivers/virtual-device.c:387 265s (process:1999): libfprint-device-DEBUG: 17:02:22.166: Device reported open completion 265s (process:1999): libfprint-device-DEBUG: 17:02:22.166: Completing action FPI_DEVICE_ACTION_OPEN in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:22.166: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:22.166: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.166: Got instructions of length 16 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.166: Received command SET_KEEP_ALIVE 0 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.166: Keep alive toggled: 0 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:22.167: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.167: Got instructions of length 19 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.167: Received command SET_ENROLL_STAGES 5 265s (process:1999): libfprint-device-DEBUG: 17:02:22.167: Device reported close completion 265s (process:1999): libfprint-device-DEBUG: 17:02:22.167: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:22.167: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s ok 265s test_delayed_open (__main__.VirtualDevice.test_delayed_open) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.167: 98152411: ../libfprint/drivers/virtual-device.c:387 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:22.167: 98152449: ../libfprint/drivers/virtual-device-listener.c:153 265s (process:1999): libfprint-device-DEBUG: 17:02:22.167: Device reported open completion 265s (process:1999): libfprint-device-DEBUG: 17:02:22.167: Completing action FPI_DEVICE_ACTION_OPEN in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:22.167: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:22.167: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.167: Got instructions of length 16 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.167: Received command IGNORED_COMMAND 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:22.168: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.168: Got instructions of length 9 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.168: Received command SLEEP 500 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.168: Processing command IGNORED_COMMAND 265s (process:1999): libfprint-device-DEBUG: 17:02:22.168: Device reported close completion 265s (process:1999): libfprint-device-DEBUG: 17:02:22.168: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:22.168: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.168: 98153482: ../libfprint/drivers/virtual-device.c:387 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.168: Processing command SLEEP 500 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.168: Sleeping 500ms 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.669: Sleeping completed 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.669: 98654786: ../libfprint/drivers/virtual-device.c:387 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:22.669: 98654882: ../libfprint/drivers/virtual-device-listener.c:153 265s (process:1999): libfprint-device-DEBUG: 17:02:22.670: Device reported open completion 265s (process:1999): libfprint-device-DEBUG: 17:02:22.670: Completing action FPI_DEVICE_ACTION_OPEN in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:22.670: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:22.670: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.670: Got instructions of length 16 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.670: Received command SET_KEEP_ALIVE 0 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.670: Keep alive toggled: 0 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:22.670: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.670: Got instructions of length 19 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.670: Received command SET_ENROLL_STAGES 5 265s (process:1999): libfprint-device-DEBUG: 17:02:22.670: Device reported close completion 265s (process:1999): libfprint-device-DEBUG: 17:02:22.670: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:22.670: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s ok 265s test_delayed_open_with_keep_alive (__main__.VirtualDevice.test_delayed_open_with_keep_alive) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.670: 98655680: ../libfprint/drivers/virtual-device.c:387 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:22.670: 98655686: ../libfprint/drivers/virtual-device-listener.c:153 265s (process:1999): libfprint-device-DEBUG: 17:02:22.670: Device reported open completion 265s (process:1999): libfprint-device-DEBUG: 17:02:22.670: Completing action FPI_DEVICE_ACTION_OPEN in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:22.670: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:22.670: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.670: Got instructions of length 16 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.670: Received command SET_KEEP_ALIVE 1 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.670: Keep alive toggled: 1 265s (process:1999): libfprint-device-DEBUG: 17:02:22.670: Device reported close completion 265s (process:1999): libfprint-device-DEBUG: 17:02:22.670: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:22.671: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:22.671: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.671: Got instructions of length 9 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.671: Received command SLEEP 500 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.671: 98656177: ../libfprint/drivers/virtual-device.c:387 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.671: Processing command SLEEP 500 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:22.671: Sleeping 500ms 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.175: Sleeping completed 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.176: 99161021: ../libfprint/drivers/virtual-device.c:387 265s (process:1999): libfprint-device-DEBUG: 17:02:23.176: Device reported open completion 265s (process:1999): libfprint-device-DEBUG: 17:02:23.176: Completing action FPI_DEVICE_ACTION_OPEN in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:23.176: Updated temperature model after 0.51 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:23.176: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.176: Got instructions of length 16 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.176: Received command SET_KEEP_ALIVE 0 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.176: Keep alive toggled: 0 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:23.176: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.176: Got instructions of length 19 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.176: Received command SET_ENROLL_STAGES 5 265s (process:1999): libfprint-device-DEBUG: 17:02:23.176: Device reported close completion 265s (process:1999): libfprint-device-DEBUG: 17:02:23.176: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:23.176: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s ok 265s test_device_features (__main__.VirtualDevice.test_device_features) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.176: 99161605: ../libfprint/drivers/virtual-device.c:387 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:23.176: 99161613: ../libfprint/drivers/virtual-device-listener.c:153 265s (process:1999): libfprint-device-DEBUG: 17:02:23.176: Device reported open completion 265s (process:1999): libfprint-device-DEBUG: 17:02:23.176: Completing action FPI_DEVICE_ACTION_OPEN in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:23.176: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:23.177: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.177: Got instructions of length 16 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.177: Received command SET_KEEP_ALIVE 0 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.177: Keep alive toggled: 0 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:23.177: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.177: Got instructions of length 19 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.177: Received command SET_ENROLL_STAGES 5 265s (process:1999): libfprint-device-DEBUG: 17:02:23.177: Device reported close completion 265s (process:1999): libfprint-device-DEBUG: 17:02:23.177: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:23.177: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s ok 265s test_device_properties (__main__.VirtualDevice.test_device_properties) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.177: 99162240: ../libfprint/drivers/virtual-device.c:387 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:23.177: 99162246: ../libfprint/drivers/virtual-device-listener.c:153 265s (process:1999): libfprint-device-DEBUG: 17:02:23.177: Device reported open completion 265s (process:1999): libfprint-device-DEBUG: 17:02:23.177: Completing action FPI_DEVICE_ACTION_OPEN in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:23.177: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:23.177: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.177: Got instructions of length 16 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.178: Received command SET_KEEP_ALIVE 0 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.178: Keep alive toggled: 0 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:23.178: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.178: Got instructions of length 19 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.178: Received command SET_ENROLL_STAGES 5 265s (process:1999): libfprint-device-DEBUG: 17:02:23.178: Device reported close completion 265s (process:1999): libfprint-device-DEBUG: 17:02:23.178: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:23.178: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s ok 265s test_device_sleep (__main__.VirtualDevice.test_device_sleep) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.178: 99163505: ../libfprint/drivers/virtual-device.c:387 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:23.178: 99163546: ../libfprint/drivers/virtual-device-listener.c:153 265s (process:1999): libfprint-device-DEBUG: 17:02:23.178: Device reported open completion 265s (process:1999): libfprint-device-DEBUG: 17:02:23.178: Completing action FPI_DEVICE_ACTION_OPEN in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:23.178: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:23.178: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.179: Got instructions of length 10 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.179: Received command SLEEP 1500 265s (process:1999): libfprint-device-DEBUG: 17:02:23.179: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.179: Processing command SLEEP 1500 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.179: Sleeping 1500ms 265s (process:1999): libfprint-device-DEBUG: 17:02:23.477: Updated temperature model after 0.30 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 265s (process:1999): libfprint-device-DEBUG: 17:02:23.479: Idle cancelling on ongoing operation! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.479: Got cancellation! 265s (process:1999): libfprint-device-DEBUG: 17:02:23.480: Device reported finger status change: FP_FINGER_STATUS_NEEDED 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.480: Virtual device scan failed with error: Operation was cancelled 265s (process:1999): libfprint-device-DEBUG: 17:02:23.480: Device reported verify completion 265s (process:1999): libfprint-device-DEBUG: 17:02:23.480: Device reported finger status change: FP_FINGER_STATUS_NONE 265s (process:1999): libfprint-device-DEBUG: 17:02:23.480: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:23.480: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:23.680: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.680: Got instructions of length 16 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.680: Received command SET_KEEP_ALIVE 0 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.680: Keep alive toggled: 0 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:23.680: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.680: Got instructions of length 19 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.680: Received command SET_ENROLL_STAGES 5 265s (process:1999): libfprint-device-DEBUG: 17:02:23.680: Device reported close completion 265s (process:1999): libfprint-device-DEBUG: 17:02:23.680: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:23.680: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 265s ok 265s test_device_sleep_before_completing_verify (__main__.VirtualDevice.test_device_sleep_before_completing_verify) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.680: 99665675: ../libfprint/drivers/virtual-device.c:387 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:23.680: 99665682: ../libfprint/drivers/virtual-device-listener.c:153 265s (process:1999): libfprint-device-DEBUG: 17:02:23.680: Device reported open completion 265s (process:1999): libfprint-device-DEBUG: 17:02:23.680: Completing action FPI_DEVICE_ACTION_OPEN in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:23.680: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:23.681: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.681: Got instructions of length 14 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.681: Received command SCAN foo-print 265s (process:1999): libfprint-device-DEBUG: 17:02:23.681: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.681: Processing command SCAN foo-print 265s (process:1999): libfprint-device-DEBUG: 17:02:23.681: Device reported finger status change: FP_FINGER_STATUS_NEEDED 265s (process:1999): libfprint-device-DEBUG: 17:02:23.681: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 265s (process:1999): libfprint-device-DEBUG: 17:02:23.681: Device reported finger status change: FP_FINGER_STATUS_NEEDED 265s (process:1999): libfprint-device-DEBUG: 17:02:23.681: Device reported enroll progress, reported 1 of 5 have been completed 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.681: Sleeping completed 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:23.681: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.681: Got instructions of length 14 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.681: Received command SCAN foo-print 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.681: Processing command SCAN foo-print 265s (process:1999): libfprint-device-DEBUG: 17:02:23.681: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 265s (process:1999): libfprint-device-DEBUG: 17:02:23.681: Device reported finger status change: FP_FINGER_STATUS_NEEDED 265s (process:1999): libfprint-device-DEBUG: 17:02:23.681: Device reported enroll progress, reported 2 of 5 have been completed 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.681: Sleeping completed 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:23.681: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.681: Got instructions of length 14 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.681: Received command SCAN foo-print 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.681: Processing command SCAN foo-print 265s (process:1999): libfprint-device-DEBUG: 17:02:23.681: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 265s (process:1999): libfprint-device-DEBUG: 17:02:23.681: Device reported finger status change: FP_FINGER_STATUS_NEEDED 265s (process:1999): libfprint-device-DEBUG: 17:02:23.681: Device reported enroll progress, reported 3 of 5 have been completed 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.681: Sleeping completed 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:23.681: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.681: Got instructions of length 14 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.681: Received command SCAN foo-print 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.681: Processing command SCAN foo-print 265s (process:1999): libfprint-device-DEBUG: 17:02:23.681: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 265s (process:1999): libfprint-device-DEBUG: 17:02:23.681: Device reported finger status change: FP_FINGER_STATUS_NEEDED 265s (process:1999): libfprint-device-DEBUG: 17:02:23.681: Device reported enroll progress, reported 4 of 5 have been completed 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.681: Sleeping completed 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:23.681: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.681: Got instructions of length 14 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.681: Received command SCAN foo-print 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.681: Processing command SCAN foo-print 265s (process:1999): libfprint-device-DEBUG: 17:02:23.682: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 265s (process:1999): libfprint-device-DEBUG: 17:02:23.682: Device reported finger status change: FP_FINGER_STATUS_NEEDED 265s (process:1999): libfprint-device-DEBUG: 17:02:23.682: Device reported enroll progress, reported 5 of 5 have been completed 265s (process:1999): libfprint-device-DEBUG: 17:02:23.682: Device reported enroll completion 265s (process:1999): libfprint-device-DEBUG: 17:02:23.682: Device reported finger status change: FP_FINGER_STATUS_NONE 265s (process:1999): libfprint-device-DEBUG: 17:02:23.682: Print for finger FP_FINGER_LEFT_RING enrolled 265s (process:1999): libfprint-device-DEBUG: 17:02:23.682: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 265s (process:1999): libfprint-device-DEBUG: 17:02:23.682: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:23.682: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.682: Got instructions of length 9 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.682: Received command SLEEP 100 265s (process:1999): libfprint-device-DEBUG: 17:02:23.682: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.682: Processing command SLEEP 100 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.682: Sleeping 100ms 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:23.682: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.682: Got instructions of length 14 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.682: Received command SCAN bar-print 265s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:23.682: Got a new connection! 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.682: Got instructions of length 9 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.682: Received command SLEEP 800 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.782: Sleeping completed 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.782: Processing command SCAN bar-print 265s (process:1999): libfprint-device-DEBUG: 17:02:23.782: Device reported finger status change: FP_FINGER_STATUS_NEEDED 265s (process:1999): libfprint-device-DEBUG: 17:02:23.782: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.782: Virtual device scanned print bar-print 265s (process:1999): libfprint-device-DEBUG: 17:02:23.782: Device reported verify result 265s (process:1999): libfprint-device-DEBUG: 17:02:23.782: Device reported finger status change: FP_FINGER_STATUS_NEEDED 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.782: Processing command SLEEP 800 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.782: Sleeping 800ms 265s (process:1999): libfprint-virtual_device-DEBUG: 17:02:23.783: Sleeping now, command queued for later: SCAN bar-print 266s (process:1999): libfprint-virtual_device-DEBUG: 17:02:24.583: Sleeping completed 266s (process:1999): libfprint-virtual_device-DEBUG: 17:02:24.584: Processing command SCAN bar-print 266s (process:1999): libfprint-device-DEBUG: 17:02:24.584: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 266s (process:1999): libfprint-virtual_device-DEBUG: 17:02:24.584: Virtual device scanned print bar-print 266s (process:1999): libfprint-device-DEBUG: 17:02:24.584: Device reported finger status change: FP_FINGER_STATUS_NEEDED 266s (process:1999): libfprint-device-DEBUG: 17:02:24.584: Device reported verify completion 266s (process:1999): libfprint-device-DEBUG: 17:02:24.584: Device reported finger status change: FP_FINGER_STATUS_NONE 266s (process:1999): libfprint-device-DEBUG: 17:02:24.584: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 266s (process:1999): libfprint-device-DEBUG: 17:02:24.584: Updated temperature model after 0.90 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 266s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:24.584: Got a new connection! 266s (process:1999): libfprint-virtual_device-DEBUG: 17:02:24.584: Got instructions of length 16 266s (process:1999): libfprint-virtual_device-DEBUG: 17:02:24.584: Received command SET_KEEP_ALIVE 0 266s (process:1999): libfprint-virtual_device-DEBUG: 17:02:24.585: Keep alive toggled: 0 266s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:24.585: Got a new connection! 266s (process:1999): libfprint-virtual_device-DEBUG: 17:02:24.585: Got instructions of length 19 266s (process:1999): libfprint-virtual_device-DEBUG: 17:02:24.585: Received command SET_ENROLL_STAGES 5 266s (process:1999): libfprint-device-DEBUG: 17:02:24.585: Device reported close completion 266s (process:1999): libfprint-device-DEBUG: 17:02:24.585: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 266s (process:1999): libfprint-device-DEBUG: 17:02:24.585: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 266s Enroll done 266s ok 266s test_device_sleep_on_cancellation (__main__.VirtualDevice.test_device_sleep_on_cancellation) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:24.585: 100570535: ../libfprint/drivers/virtual-device.c:387 266s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:24.585: 100570576: ../libfprint/drivers/virtual-device-listener.c:153 266s (process:1999): libfprint-device-DEBUG: 17:02:24.585: Device reported open completion 266s (process:1999): libfprint-device-DEBUG: 17:02:24.585: Completing action FPI_DEVICE_ACTION_OPEN in idle! 266s (process:1999): libfprint-device-DEBUG: 17:02:24.585: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 266s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:24.586: Got a new connection! 266s (process:1999): libfprint-virtual_device-DEBUG: 17:02:24.586: Got instructions of length 26 266s (process:1999): libfprint-virtual_device-DEBUG: 17:02:24.586: Received command SET_CANCELLATION_ENABLED 0 266s (process:1999): libfprint-virtual_device-DEBUG: 17:02:24.586: Cancellation support toggled: 0 266s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:24.586: Got a new connection! 266s (process:1999): libfprint-virtual_device-DEBUG: 17:02:24.586: Got instructions of length 10 266s (process:1999): libfprint-virtual_device-DEBUG: 17:02:24.586: Received command SLEEP 1500 266s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:24.586: Got a new connection! 266s (process:1999): libfprint-virtual_device-DEBUG: 17:02:24.586: Got instructions of length 14 266s (process:1999): libfprint-virtual_device-DEBUG: 17:02:24.586: Received command SCAN foo-print 266s (process:1999): libfprint-device-DEBUG: 17:02:24.586: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 266s (process:1999): libfprint-virtual_device-DEBUG: 17:02:24.586: Processing command SLEEP 1500 266s (process:1999): libfprint-virtual_device-DEBUG: 17:02:24.586: Sleeping 1500ms 266s (process:1999): libfprint-device-DEBUG: 17:02:24.886: Idle cancelling on ongoing operation! 268s Executing: libfprint-2/virtual-device.test 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.087: Sleeping completed 268s (process:1999): libfprint-device-DEBUG: 17:02:26.088: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.088: Virtual device scan failed with error: Operation was cancelled 268s (process:1999): libfprint-device-DEBUG: 17:02:26.088: Device reported verify completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.088: Device reported finger status change: FP_FINGER_STATUS_NONE 268s (process:1999): libfprint-device-DEBUG: 17:02:26.088: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.088: Updated temperature model after 1.50 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.088: Processing command SCAN foo-print 268s (process:1999): libfprint-device-DEBUG: 17:02:26.088: Device reported close completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.088: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.088: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s ok 268s test_enroll (__main__.VirtualDevice.test_enroll) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.088: 102073512: ../libfprint/drivers/virtual-device.c:387 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.088: 102073522: ../libfprint/drivers/virtual-device-listener.c:153 268s (process:1999): libfprint-device-DEBUG: 17:02:26.088: Device reported open completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.088: Completing action FPI_DEVICE_ACTION_OPEN in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.088: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.088: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.088: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.088: Received command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.088: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.088: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.088: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.088: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.088: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.088: Device reported enroll progress, reported 1 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.089: Sleeping completed 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.089: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.089: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.089: Received command SCAN testprint 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.089: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.089: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.089: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.089: Device reported enroll progress, reported 2 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.089: Sleeping completed 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.089: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.089: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.089: Received command SCAN testprint 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.089: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.089: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.089: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.089: Device reported enroll progress, reported 3 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.089: Sleeping completed 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.089: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.089: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.089: Received command SCAN testprint 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.089: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.089: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.089: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.089: Device reported enroll progress, reported 4 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.089: Sleeping completed 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.089: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.089: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.089: Received command SCAN testprint 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.089: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.089: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.089: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.089: Device reported enroll progress, reported 5 of 5 have been completed 268s (process:1999): libfprint-device-DEBUG: 17:02:26.089: Device reported enroll completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.089: Device reported finger status change: FP_FINGER_STATUS_NONE 268s (process:1999): libfprint-device-DEBUG: 17:02:26.089: Print for finger FP_FINGER_LEFT_LITTLE enrolled 268s (process:1999): libfprint-device-DEBUG: 17:02:26.089: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.089: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.089: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.089: Got instructions of length 16 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.089: Received command SET_KEEP_ALIVE 0 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.089: Keep alive toggled: 0 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.089: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.089: Got instructions of length 19 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.089: Received command SET_ENROLL_STAGES 5 268s (process:1999): libfprint-device-DEBUG: 17:02:26.089: Device reported close completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.089: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.089: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s Enroll done 268s ok 268s test_enroll_script (__main__.VirtualDevice.test_enroll_script) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.090: 102074910: ../libfprint/drivers/virtual-device.c:387 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.090: 102074916: ../libfprint/drivers/virtual-device-listener.c:153 268s (process:1999): libfprint-device-DEBUG: 17:02:26.090: Device reported open completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.090: Completing action FPI_DEVICE_ACTION_OPEN in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.090: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.090: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.090: Got instructions of length 19 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.090: Received command SET_ENROLL_STAGES 8 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.090: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.090: Got instructions of length 13 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.090: Received command SCAN print-id 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.090: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.090: Got instructions of length 13 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.090: Received command SCAN print-id 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.090: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.090: Got instructions of length 7 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.090: Received command RETRY 1 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.090: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.090: Got instructions of length 13 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.090: Received command SCAN print-id 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.090: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.090: Got instructions of length 7 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.090: Received command RETRY 3 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.090: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.090: Got instructions of length 13 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.090: Received command SCAN print-id 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.090: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.090: Got instructions of length 7 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.090: Received command RETRY 2 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.090: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.090: Got instructions of length 13 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.090: Received command SCAN print-id 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.090: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.090: Got instructions of length 8 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.090: Received command SLEEP 10 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.090: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.090: Got instructions of length 8 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.090: Received command SLEEP 20 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.091: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.091: Got instructions of length 7 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.091: Received command RETRY 0 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.091: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.091: Got instructions of length 7 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.091: Received command RETRY 3 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.091: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.091: Got instructions of length 13 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.091: Received command SCAN print-id 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.091: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.091: Got instructions of length 15 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.091: Received command SCAN another-id 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.091: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.092: Got instructions of length 13 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.092: Received command SCAN print-id 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.092: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.092: Got instructions of length 13 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.092: Received command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.092: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.092: Processing command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.092: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.092: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.092: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.092: Device reported enroll progress, reported 1 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.092: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.092: Processing command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.092: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.092: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.092: Device reported enroll progress, reported 2 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.092: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.092: Processing command RETRY 1 268s (process:1999): libfprint-device-DEBUG: 17:02:26.092: Device reported enroll progress, reported 2 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.093: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.093: Processing command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.093: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.093: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.093: Device reported enroll progress, reported 3 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.093: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.093: Processing command RETRY 3 268s (process:1999): libfprint-device-DEBUG: 17:02:26.093: Device reported enroll progress, reported 3 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.093: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.093: Processing command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.093: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.093: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.093: Device reported enroll progress, reported 4 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.093: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.093: Processing command RETRY 2 268s (process:1999): libfprint-device-DEBUG: 17:02:26.093: Device reported enroll progress, reported 4 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.093: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.093: Processing command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.093: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.093: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.093: Device reported enroll progress, reported 5 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.093: Processing command SLEEP 10 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.093: Sleeping 10ms 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.103: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.103: Processing command SLEEP 20 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.103: Sleeping 20ms 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.124: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.124: Processing command RETRY 0 268s (process:1999): libfprint-device-DEBUG: 17:02:26.124: Device reported enroll progress, reported 5 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.124: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.124: Processing command RETRY 3 268s (process:1999): libfprint-device-DEBUG: 17:02:26.124: Device reported enroll progress, reported 5 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.124: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.124: Processing command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.124: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.124: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.124: Device reported enroll progress, reported 6 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.124: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.124: Processing command SCAN another-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.124: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.124: Device reported enroll progress, reported 6 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.124: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.124: Processing command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.124: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.124: Device reported enroll progress, reported 7 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.124: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.124: Processing command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.124: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.124: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.124: Device reported enroll progress, reported 8 of 8 have been completed 268s (process:1999): libfprint-device-DEBUG: 17:02:26.124: Device reported enroll completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.125: Device reported finger status change: FP_FINGER_STATUS_NONE 268s (process:1999): libfprint-device-DEBUG: 17:02:26.125: Print for finger FP_FINGER_UNKNOWN enrolled 268s (process:1999): libfprint-device-DEBUG: 17:02:26.125: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.125: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.125: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.125: Got instructions of length 16 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.125: Received command SET_KEEP_ALIVE 0 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.125: Keep alive toggled: 0 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.125: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.125: Got instructions of length 19 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.125: Received command SET_ENROLL_STAGES 5 268s (process:1999): libfprint-device-DEBUG: 17:02:26.125: Device reported close completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.125: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.125: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s ok 268s test_enroll_script_interactive (__main__.VirtualDevice.test_enroll_script_interactive) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.126: 102111078: ../libfprint/drivers/virtual-device.c:387 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.126: 102111118: ../libfprint/drivers/virtual-device-listener.c:153 268s (process:1999): libfprint-device-DEBUG: 17:02:26.126: Device reported open completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.126: Completing action FPI_DEVICE_ACTION_OPEN in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.126: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.126: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.126: Got instructions of length 8 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.126: Received command SLEEP 50 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.126: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.126: Got instructions of length 13 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.126: Received command SCAN print-id 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.126: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.126: Got instructions of length 13 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.126: Received command SCAN print-id 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.126: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.126: Got instructions of length 7 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.126: Received command RETRY 1 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.126: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.126: Got instructions of length 13 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.126: Received command SCAN print-id 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.126: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.126: Got instructions of length 8 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.126: Received command SLEEP 50 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.127: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.127: Got instructions of length 13 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.127: Received command SCAN print-id 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.127: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.127: Got instructions of length 7 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.127: Received command RETRY 2 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.127: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.127: Got instructions of length 15 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.127: Received command SCAN another-id 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.127: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.127: Got instructions of length 13 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.127: Received command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.127: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.127: Processing command SLEEP 50 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.127: Sleeping 50ms 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.178: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.178: Processing command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.178: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.178: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.178: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.178: Device reported enroll progress, reported 1 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.178: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.178: Processing command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.178: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.178: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.178: Device reported enroll progress, reported 2 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.178: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.178: Processing command RETRY 1 268s (process:1999): libfprint-device-DEBUG: 17:02:26.178: Device reported enroll progress, reported 2 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.178: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.178: Processing command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.178: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.178: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.178: Device reported enroll progress, reported 3 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.178: Processing command SLEEP 50 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.178: Sleeping 50ms 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.229: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.229: Processing command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.229: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.229: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.229: Device reported enroll progress, reported 4 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.229: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.229: Processing command RETRY 2 268s (process:1999): libfprint-device-DEBUG: 17:02:26.229: Device reported enroll progress, reported 4 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.229: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.229: Processing command SCAN another-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.229: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.229: Device reported enroll progress, reported 4 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.229: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.229: Processing command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.229: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.229: Device reported enroll progress, reported 5 of 5 have been completed 268s (process:1999): libfprint-device-DEBUG: 17:02:26.229: Device reported enroll completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.229: Device reported finger status change: FP_FINGER_STATUS_NONE 268s (process:1999): libfprint-device-DEBUG: 17:02:26.229: Print for finger FP_FINGER_UNKNOWN enrolled 268s (process:1999): libfprint-device-DEBUG: 17:02:26.229: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.229: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.229: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.230: Got instructions of length 16 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.230: Received command SET_KEEP_ALIVE 0 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.230: Keep alive toggled: 0 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.230: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.230: Got instructions of length 19 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.230: Received command SET_ENROLL_STAGES 5 268s (process:1999): libfprint-device-DEBUG: 17:02:26.230: Device reported close completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.230: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.230: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s ok 268s test_enroll_verify_error (__main__.VirtualDevice.test_enroll_verify_error) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.230: 102215169: ../libfprint/drivers/virtual-device.c:387 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.230: 102215176: ../libfprint/drivers/virtual-device-listener.c:153 268s (process:1999): libfprint-device-DEBUG: 17:02:26.230: Device reported open completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.230: Completing action FPI_DEVICE_ACTION_OPEN in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.230: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.230: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.230: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.230: Received command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.230: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.230: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.230: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.230: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.230: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.230: Device reported enroll progress, reported 1 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.230: Sleeping completed 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.230: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.230: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.230: Received command SCAN testprint 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.230: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.230: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.230: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.230: Device reported enroll progress, reported 2 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.230: Sleeping completed 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.230: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.230: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.230: Received command SCAN testprint 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.230: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.230: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.230: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.230: Device reported enroll progress, reported 3 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.230: Sleeping completed 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.230: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.230: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.230: Received command SCAN testprint 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.230: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.230: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.230: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.230: Device reported enroll progress, reported 4 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.230: Sleeping completed 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.231: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.231: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.231: Received command SCAN testprint 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.231: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.231: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.231: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.231: Device reported enroll progress, reported 5 of 5 have been completed 268s (process:1999): libfprint-device-DEBUG: 17:02:26.231: Device reported enroll completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.231: Device reported finger status change: FP_FINGER_STATUS_NONE 268s (process:1999): libfprint-device-DEBUG: 17:02:26.231: Print for finger FP_FINGER_LEFT_RING enrolled 268s (process:1999): libfprint-device-DEBUG: 17:02:26.231: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.231: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.231: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.231: Got instructions of length 7 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.231: Received command ERROR 0 268s (process:1999): libfprint-device-DEBUG: 17:02:26.231: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.231: Processing command ERROR 0 268s (process:1999): libfprint-device-DEBUG: 17:02:26.231: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.231: Virtual device scan failed with error: An unspecified error occurred! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.231: Device reported verify completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.231: Device reported finger status change: FP_FINGER_STATUS_NONE 268s (process:1999): libfprint-device-DEBUG: 17:02:26.232: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.232: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.232: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.232: Got instructions of length 16 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.232: Received command SET_KEEP_ALIVE 0 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.232: Keep alive toggled: 0 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.232: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.232: Got instructions of length 19 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.232: Received command SET_ENROLL_STAGES 5 268s (process:1999): libfprint-device-DEBUG: 17:02:26.232: Device reported close completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.232: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.232: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s Enroll done 268s ok 268s test_enroll_verify_match (__main__.VirtualDevice.test_enroll_verify_match) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.232: 102217514: ../libfprint/drivers/virtual-device.c:387 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.232: 102217521: ../libfprint/drivers/virtual-device-listener.c:153 268s (process:1999): libfprint-device-DEBUG: 17:02:26.232: Device reported open completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.232: Completing action FPI_DEVICE_ACTION_OPEN in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.232: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.232: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.232: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.232: Received command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.232: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.232: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.232: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.232: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.232: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.232: Device reported enroll progress, reported 1 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.232: Sleeping completed 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.232: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.233: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.233: Received command SCAN testprint 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.233: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Device reported enroll progress, reported 2 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.233: Sleeping completed 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.233: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.233: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.233: Received command SCAN testprint 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.233: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Device reported enroll progress, reported 3 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.233: Sleeping completed 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.233: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.233: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.233: Received command SCAN testprint 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.233: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Device reported enroll progress, reported 4 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.233: Sleeping completed 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.233: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.233: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.233: Received command SCAN testprint 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.233: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Device reported enroll progress, reported 5 of 5 have been completed 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Device reported enroll completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Device reported finger status change: FP_FINGER_STATUS_NONE 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Print for finger FP_FINGER_LEFT_THUMB enrolled 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.233: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.233: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.233: Received command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.233: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.233: Virtual device scanned print testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Device reported verify result 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Device reported verify completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Device reported finger status change: FP_FINGER_STATUS_NONE 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.233: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.233: Got instructions of length 16 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.233: Received command SET_KEEP_ALIVE 0 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.233: Keep alive toggled: 0 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.233: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.233: Got instructions of length 19 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.233: Received command SET_ENROLL_STAGES 5 268s (process:1999): libfprint-device-DEBUG: 17:02:26.233: Device reported close completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s Enroll done 268s ok 268s test_enroll_verify_no_match (__main__.VirtualDevice.test_enroll_verify_no_match) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.234: 102218985: ../libfprint/drivers/virtual-device.c:387 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.234: 102218992: ../libfprint/drivers/virtual-device-listener.c:153 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Device reported open completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Completing action FPI_DEVICE_ACTION_OPEN in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.234: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.234: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.234: Received command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.234: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Device reported enroll progress, reported 1 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.234: Sleeping completed 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.234: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.234: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.234: Received command SCAN testprint 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.234: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Device reported enroll progress, reported 2 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.234: Sleeping completed 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.234: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.234: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.234: Received command SCAN testprint 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.234: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Device reported enroll progress, reported 3 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.234: Sleeping completed 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.234: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.234: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.234: Received command SCAN testprint 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.234: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Device reported enroll progress, reported 4 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.234: Sleeping completed 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.234: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.234: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.234: Received command SCAN testprint 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.234: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Device reported enroll progress, reported 5 of 5 have been completed 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Device reported enroll completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Device reported finger status change: FP_FINGER_STATUS_NONE 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Print for finger FP_FINGER_LEFT_RING enrolled 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.234: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.234: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.234: Got instructions of length 18 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.234: Received command SCAN not-testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.235: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.235: Processing command SCAN not-testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.235: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.235: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.235: Virtual device scanned print not-testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.235: Device reported verify result 268s (process:1999): libfprint-device-DEBUG: 17:02:26.235: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.235: Device reported verify completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.235: Device reported finger status change: FP_FINGER_STATUS_NONE 268s (process:1999): libfprint-device-DEBUG: 17:02:26.235: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.235: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.235: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.235: Got instructions of length 16 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.235: Received command SET_KEEP_ALIVE 0 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.235: Keep alive toggled: 0 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.235: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.235: Got instructions of length 19 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.235: Received command SET_ENROLL_STAGES 5 268s (process:1999): libfprint-device-DEBUG: 17:02:26.235: Device reported close completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.235: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.235: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s Enroll done 268s ok 268s test_enroll_verify_retry (__main__.VirtualDevice.test_enroll_verify_retry) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.236: 102220994: ../libfprint/drivers/virtual-device.c:387 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.236: 102221034: ../libfprint/drivers/virtual-device-listener.c:153 268s (process:1999): libfprint-device-DEBUG: 17:02:26.236: Device reported open completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.236: Completing action FPI_DEVICE_ACTION_OPEN in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.236: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.236: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.236: Got instructions of length 7 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.236: Received command RETRY 1 268s (process:1999): libfprint-device-DEBUG: 17:02:26.236: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.236: Processing command RETRY 1 268s (process:1999): libfprint-device-DEBUG: 17:02:26.236: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.236: Virtual device scan failed with error: The swipe was too short, please try again. 268s (process:1999): libfprint-device-DEBUG: 17:02:26.236: Device reported verify result 268s (process:1999): libfprint-device-DEBUG: 17:02:26.236: Device reported verify completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.236: Device reported finger status change: FP_FINGER_STATUS_NONE 268s (process:1999): libfprint-device-DEBUG: 17:02:26.236: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.237: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.237: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.237: Got instructions of length 16 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.237: Received command SET_KEEP_ALIVE 0 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.237: Keep alive toggled: 0 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.237: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.237: Got instructions of length 19 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.237: Received command SET_ENROLL_STAGES 5 268s (process:1999): libfprint-device-DEBUG: 17:02:26.237: Device reported close completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.237: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.237: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s ok 268s test_enroll_verify_script (__main__.VirtualDevice.test_enroll_verify_script) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.237: 102222752: ../libfprint/drivers/virtual-device.c:387 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.237: 102222794: ../libfprint/drivers/virtual-device-listener.c:153 268s (process:1999): libfprint-device-DEBUG: 17:02:26.237: Device reported open completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.238: Completing action FPI_DEVICE_ACTION_OPEN in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.238: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.238: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.238: Got instructions of length 19 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.238: Received command SET_ENROLL_STAGES 8 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.238: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.238: Got instructions of length 13 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.238: Received command SCAN print-id 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.238: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.238: Got instructions of length 13 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.238: Received command SCAN print-id 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.238: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.238: Got instructions of length 7 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.238: Received command RETRY 1 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.239: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.239: Got instructions of length 13 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.239: Received command SCAN print-id 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.239: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.239: Got instructions of length 7 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.239: Received command RETRY 3 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.239: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.239: Got instructions of length 13 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.239: Received command SCAN print-id 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.239: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.239: Got instructions of length 7 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.239: Received command RETRY 2 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.239: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.240: Got instructions of length 13 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.240: Received command SCAN print-id 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.240: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.240: Got instructions of length 8 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.240: Received command SLEEP 10 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.240: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.240: Got instructions of length 8 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.240: Received command SLEEP 20 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.240: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.240: Got instructions of length 7 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.240: Received command RETRY 0 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.240: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.240: Got instructions of length 7 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.240: Received command RETRY 3 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.241: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.241: Got instructions of length 13 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.241: Received command SCAN print-id 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.241: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.241: Got instructions of length 15 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.241: Received command SCAN another-id 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.241: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.241: Got instructions of length 13 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.241: Received command SCAN print-id 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.241: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.241: Got instructions of length 13 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.241: Received command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.241: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.241: Processing command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.241: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.241: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.241: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.241: Device reported enroll progress, reported 1 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.241: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.241: Processing command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.241: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.241: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.241: Device reported enroll progress, reported 2 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.241: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.241: Processing command RETRY 1 268s (process:1999): libfprint-device-DEBUG: 17:02:26.241: Device reported enroll progress, reported 2 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.241: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.241: Processing command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.241: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.241: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.241: Device reported enroll progress, reported 3 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.241: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.241: Processing command RETRY 3 268s (process:1999): libfprint-device-DEBUG: 17:02:26.241: Device reported enroll progress, reported 3 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.241: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.241: Processing command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.241: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.241: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.241: Device reported enroll progress, reported 4 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.241: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.241: Processing command RETRY 2 268s (process:1999): libfprint-device-DEBUG: 17:02:26.241: Device reported enroll progress, reported 4 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.241: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.241: Processing command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.241: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.241: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.241: Device reported enroll progress, reported 5 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.241: Processing command SLEEP 10 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.241: Sleeping 10ms 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.251: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.251: Processing command SLEEP 20 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.251: Sleeping 20ms 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.271: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.271: Processing command RETRY 0 268s (process:1999): libfprint-device-DEBUG: 17:02:26.271: Device reported enroll progress, reported 5 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.271: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.271: Processing command RETRY 3 268s (process:1999): libfprint-device-DEBUG: 17:02:26.271: Device reported enroll progress, reported 5 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.271: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.271: Processing command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.271: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.271: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.271: Device reported enroll progress, reported 6 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.271: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.271: Processing command SCAN another-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.271: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.271: Device reported enroll progress, reported 6 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.271: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.271: Processing command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.271: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.271: Device reported enroll progress, reported 7 of 8 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.271: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.271: Processing command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.271: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.271: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.271: Device reported enroll progress, reported 8 of 8 have been completed 268s (process:1999): libfprint-device-DEBUG: 17:02:26.271: Device reported enroll completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.271: Device reported finger status change: FP_FINGER_STATUS_NONE 268s (process:1999): libfprint-device-DEBUG: 17:02:26.271: Print for finger FP_FINGER_UNKNOWN enrolled 268s (process:1999): libfprint-device-DEBUG: 17:02:26.271: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.271: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.272: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.272: Got instructions of length 7 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.272: Received command RETRY 2 268s (process:1999): libfprint-device-DEBUG: 17:02:26.272: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.272: Processing command RETRY 2 268s (process:1999): libfprint-device-DEBUG: 17:02:26.272: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.272: Virtual device scan failed with error: The finger was not centered properly, please try again. 268s (process:1999): libfprint-device-DEBUG: 17:02:26.272: Device reported verify result 268s (process:1999): libfprint-device-DEBUG: 17:02:26.272: Device reported verify completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.272: Device reported finger status change: FP_FINGER_STATUS_NONE 268s (process:1999): libfprint-device-DEBUG: 17:02:26.272: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.272: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.272: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.272: Got instructions of length 8 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.272: Received command SLEEP 50 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.272: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.272: Got instructions of length 7 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.272: Received command RETRY 1 268s (process:1999): libfprint-device-DEBUG: 17:02:26.272: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.272: Processing command SLEEP 50 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.272: Sleeping 50ms 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.322: Sleeping completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.322: Processing command RETRY 1 268s (process:1999): libfprint-device-DEBUG: 17:02:26.322: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.322: Virtual device scan failed with error: The swipe was too short, please try again. 268s (process:1999): libfprint-device-DEBUG: 17:02:26.322: Device reported verify result 268s (process:1999): libfprint-device-DEBUG: 17:02:26.322: Device reported verify completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.322: Device reported finger status change: FP_FINGER_STATUS_NONE 268s (process:1999): libfprint-device-DEBUG: 17:02:26.322: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.322: Updated temperature model after 0.05 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.323: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.323: Got instructions of length 15 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.323: Received command SCAN another-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.323: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.323: Processing command SCAN another-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.323: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.323: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.323: Virtual device scanned print another-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.323: Device reported verify result 268s (process:1999): libfprint-device-DEBUG: 17:02:26.323: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.323: Device reported verify completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.323: Device reported finger status change: FP_FINGER_STATUS_NONE 268s (process:1999): libfprint-device-DEBUG: 17:02:26.323: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.323: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.323: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.323: Got instructions of length 13 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.323: Received command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.323: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.323: Processing command SCAN print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.323: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.323: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.323: Virtual device scanned print print-id 268s (process:1999): libfprint-device-DEBUG: 17:02:26.323: Device reported verify result 268s (process:1999): libfprint-device-DEBUG: 17:02:26.323: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.323: Device reported verify completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.323: Device reported finger status change: FP_FINGER_STATUS_NONE 268s (process:1999): libfprint-device-DEBUG: 17:02:26.323: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.323: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.323: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.323: Got instructions of length 16 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.323: Received command SET_KEEP_ALIVE 0 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.323: Keep alive toggled: 0 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.323: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.323: Got instructions of length 19 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.323: Received command SET_ENROLL_STAGES 5 268s (process:1999): libfprint-device-DEBUG: 17:02:26.323: Device reported close completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.323: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.323: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s ok 268s test_enroll_with_retry (__main__.VirtualDevice.test_enroll_with_retry) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.323: 102308643: ../libfprint/drivers/virtual-device.c:387 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.323: 102308650: ../libfprint/drivers/virtual-device-listener.c:153 268s (process:1999): libfprint-device-DEBUG: 17:02:26.323: Device reported open completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.323: Completing action FPI_DEVICE_ACTION_OPEN in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.323: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.323: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.323: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.323: Received command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.324: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.324: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.324: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.324: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.324: Device reported enroll progress, reported 1 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Sleeping completed 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.324: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Received command SCAN testprint 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.324: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.324: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.324: Device reported enroll progress, reported 2 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Sleeping completed 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.324: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Got instructions of length 7 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Received command RETRY 1 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Processing command RETRY 1 268s (process:1999): libfprint-device-DEBUG: 17:02:26.324: Device reported enroll progress, reported 2 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Sleeping completed 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.324: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Received command SCAN testprint 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.324: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.324: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.324: Device reported enroll progress, reported 3 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Sleeping completed 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.324: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Received command SCAN testprint 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.324: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.324: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.324: Device reported enroll progress, reported 4 of 5 have been completed 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Sleeping completed 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.324: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Received command SCAN testprint 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.324: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.324: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.324: Device reported enroll progress, reported 5 of 5 have been completed 268s (process:1999): libfprint-device-DEBUG: 17:02:26.324: Device reported enroll completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.324: Device reported finger status change: FP_FINGER_STATUS_NONE 268s (process:1999): libfprint-device-DEBUG: 17:02:26.324: Print for finger FP_FINGER_LEFT_LITTLE enrolled 268s (process:1999): libfprint-device-DEBUG: 17:02:26.324: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.324: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.324: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Got instructions of length 16 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Received command SET_KEEP_ALIVE 0 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Keep alive toggled: 0 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.324: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Got instructions of length 19 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.324: Received command SET_ENROLL_STAGES 5 268s (process:1999): libfprint-device-DEBUG: 17:02:26.325: Device reported close completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.325: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.325: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s Enroll done 268s ok 268s test_finger_status (__main__.VirtualDevice.test_finger_status) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.325: 102310027: ../libfprint/drivers/virtual-device.c:387 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.325: 102310034: ../libfprint/drivers/virtual-device-listener.c:153 268s (process:1999): libfprint-device-DEBUG: 17:02:26.325: Device reported open completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.325: Completing action FPI_DEVICE_ACTION_OPEN in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.325: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-device-DEBUG: 17:02:26.325: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-device-DEBUG: 17:02:26.325: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.325: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.325: Got instructions of length 8 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.325: Received command FINGER 1 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.325: Processing command FINGER 1 268s (process:1999): libfprint-device-DEBUG: 17:02:26.325: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.325: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.325: Got instructions of length 8 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.325: Received command FINGER 0 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.325: Processing command FINGER 0 268s (process:1999): libfprint-device-DEBUG: 17:02:26.325: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.325: Idle cancelling on ongoing operation! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.325: Got cancellation! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.325: Virtual device scan failed with error: Operation was cancelled 268s (process:1999): libfprint-device-DEBUG: 17:02:26.325: Device reported verify completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.325: Device reported finger status change: FP_FINGER_STATUS_NONE 268s (process:1999): libfprint-device-DEBUG: 17:02:26.325: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.325: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.325: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.325: Got instructions of length 16 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.325: Received command SET_KEEP_ALIVE 0 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.325: Keep alive toggled: 0 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.325: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.325: Got instructions of length 19 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.325: Received command SET_ENROLL_STAGES 5 268s (process:1999): libfprint-device-DEBUG: 17:02:26.325: Device reported close completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.325: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.325: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s ok 268s test_finger_status_after_sleep (__main__.VirtualDevice.test_finger_status_after_sleep) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.325: 102310744: ../libfprint/drivers/virtual-device.c:387 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.325: 102310750: ../libfprint/drivers/virtual-device-listener.c:153 268s (process:1999): libfprint-device-DEBUG: 17:02:26.325: Device reported open completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.325: Completing action FPI_DEVICE_ACTION_OPEN in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.325: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.326: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.326: Got instructions of length 8 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.326: Received command SLEEP 10 268s (process:1999): libfprint-device-DEBUG: 17:02:26.326: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.326: Processing command SLEEP 10 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.326: Sleeping 10ms 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.336: Sleeping completed 268s (process:1999): libfprint-device-DEBUG: 17:02:26.336: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.336: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.336: Got instructions of length 8 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.336: Received command FINGER 1 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.336: Processing command FINGER 1 268s (process:1999): libfprint-device-DEBUG: 17:02:26.336: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.336: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.336: Got instructions of length 8 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.336: Received command FINGER 0 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.336: Processing command FINGER 0 268s (process:1999): libfprint-device-DEBUG: 17:02:26.336: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.336: Idle cancelling on ongoing operation! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.336: Got cancellation! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.336: Virtual device scan failed with error: Operation was cancelled 268s (process:1999): libfprint-device-DEBUG: 17:02:26.336: Device reported verify completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.336: Device reported finger status change: FP_FINGER_STATUS_NONE 268s (process:1999): libfprint-device-DEBUG: 17:02:26.336: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.336: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.336: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.336: Got instructions of length 16 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.336: Received command SET_KEEP_ALIVE 0 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.336: Keep alive toggled: 0 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.336: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.336: Got instructions of length 19 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.336: Received command SET_ENROLL_STAGES 5 268s (process:1999): libfprint-device-DEBUG: 17:02:26.336: Device reported close completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.336: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.336: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s ok 268s test_identify_unsupported (__main__.VirtualDevice.test_identify_unsupported) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.336: 102321715: ../libfprint/drivers/virtual-device.c:387 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.336: 102321722: ../libfprint/drivers/virtual-device-listener.c:153 268s (process:1999): libfprint-device-DEBUG: 17:02:26.336: Device reported open completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.336: Completing action FPI_DEVICE_ACTION_OPEN in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.336: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.337: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.337: Got instructions of length 16 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.337: Received command SET_KEEP_ALIVE 0 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.337: Keep alive toggled: 0 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.337: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.337: Got instructions of length 19 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.337: Received command SET_ENROLL_STAGES 5 268s (process:1999): libfprint-device-DEBUG: 17:02:26.337: Device reported close completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.337: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.337: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s ok 268s test_open_error (__main__.VirtualDevice.test_open_error) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.337: 102322287: ../libfprint/drivers/virtual-device.c:387 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.337: 102322293: ../libfprint/drivers/virtual-device-listener.c:153 268s (process:1999): libfprint-device-DEBUG: 17:02:26.337: Device reported open completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.337: Completing action FPI_DEVICE_ACTION_OPEN in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.337: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.337: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.337: Got instructions of length 16 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.337: Received command IGNORED_COMMAND 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.337: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.337: Got instructions of length 7 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.337: Received command ERROR 5 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.337: Processing command IGNORED_COMMAND 268s (process:1999): libfprint-device-DEBUG: 17:02:26.337: Device reported close completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.337: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.337: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.337: 102322742: ../libfprint/drivers/virtual-device.c:387 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.337: Processing command ERROR 5 268s (process:1999): libfprint-device-DEBUG: 17:02:26.337: Device reported open completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.337: Completing action FPI_DEVICE_ACTION_OPEN in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.337: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s ok 268s test_open_error_with_keep_alive (__main__.VirtualDevice.test_open_error_with_keep_alive) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.337: 102322837: ../libfprint/drivers/virtual-device.c:387 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.337: 102322843: ../libfprint/drivers/virtual-device-listener.c:153 268s (process:1999): libfprint-device-DEBUG: 17:02:26.337: Device reported open completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.338: Completing action FPI_DEVICE_ACTION_OPEN in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.338: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.338: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.338: Got instructions of length 16 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.338: Received command SET_KEEP_ALIVE 1 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.338: Keep alive toggled: 1 268s (process:1999): libfprint-device-DEBUG: 17:02:26.338: Device reported close completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.338: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.338: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.338: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.338: Got instructions of length 7 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.338: Received command ERROR 5 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.338: 102323152: ../libfprint/drivers/virtual-device.c:387 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.338: Processing command ERROR 5 268s (process:1999): libfprint-device-DEBUG: 17:02:26.338: Device reported open completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.338: Completing action FPI_DEVICE_ACTION_OPEN in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.338: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s ok 268s test_quick_enroll (__main__.VirtualDevice.test_quick_enroll) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.338: 102323235: ../libfprint/drivers/virtual-device.c:387 268s (process:1999): libfprint-device-DEBUG: 17:02:26.338: Device reported open completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.338: Completing action FPI_DEVICE_ACTION_OPEN in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.338: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.338: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.338: Got instructions of length 19 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.338: Received command SET_ENROLL_STAGES 1 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.338: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.338: Got instructions of length 14 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.338: Received command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.338: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.338: Processing command SCAN testprint 268s (process:1999): libfprint-device-DEBUG: 17:02:26.338: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.338: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 268s (process:1999): libfprint-device-DEBUG: 17:02:26.338: Device reported finger status change: FP_FINGER_STATUS_NEEDED 268s (process:1999): libfprint-device-DEBUG: 17:02:26.338: Device reported enroll progress, reported 1 of 1 have been completed 268s (process:1999): libfprint-device-DEBUG: 17:02:26.338: Device reported enroll completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.338: Device reported finger status change: FP_FINGER_STATUS_NONE 268s (process:1999): libfprint-device-DEBUG: 17:02:26.338: Print for finger FP_FINGER_LEFT_LITTLE enrolled 268s (process:1999): libfprint-device-DEBUG: 17:02:26.338: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.338: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.338: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.338: Got instructions of length 16 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.338: Received command SET_KEEP_ALIVE 0 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.338: Keep alive toggled: 0 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.338: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.338: Got instructions of length 19 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.338: Received command SET_ENROLL_STAGES 5 268s (process:1999): libfprint-device-DEBUG: 17:02:26.338: Device reported close completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.338: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.338: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 268s Enroll done 268s ok 268s (process:1999): libfprint-context-DEBUG: 17:02:26.339: Initializing FpContext (libfprint version 1.94.7+tod1) 268s (process:1999): libfprint-tod-DEBUG: 17:02:26.339: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 268s (process:1999): libfprint-context-DEBUG: 17:02:26.340: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-d15u894n/virtual-device.socket 268s (process:1999): libfprint-context-DEBUG: 17:02:26.340: created 268s (process:1999): libfprint-device-DEBUG: 17:02:26.340: Device reported probe completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.340: Completing action FPI_DEVICE_ACTION_PROBE in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.340: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 268s test_capture (__main__.VirtualDeviceBusyDeviceOperations.test_capture) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.340: 102325425: ../libfprint/drivers/virtual-device.c:387 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.340: 102325468: ../libfprint/drivers/virtual-device-listener.c:153 268s (process:1999): libfprint-device-DEBUG: 17:02:26.340: Device reported open completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.340: Completing action FPI_DEVICE_ACTION_OPEN in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.340: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.340: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.340: Got instructions of length 9 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.340: Received command SLEEP 200 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.341: Processing command SLEEP 200 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.341: Sleeping 200ms 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.541: Sleeping completed 268s (process:1999): libfprint-device-DEBUG: 17:02:26.541: Device reported close completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.541: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.541: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 268s ok 268s test_close (__main__.VirtualDeviceBusyDeviceOperations.test_close) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.541: 102526716: ../libfprint/drivers/virtual-device.c:387 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.541: 102526725: ../libfprint/drivers/virtual-device-listener.c:153 268s (process:1999): libfprint-device-DEBUG: 17:02:26.541: Device reported open completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.541: Completing action FPI_DEVICE_ACTION_OPEN in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.541: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.542: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.542: Got instructions of length 9 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.542: Received command SLEEP 200 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.542: Processing command SLEEP 200 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.542: Sleeping 200ms 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.742: Sleeping completed 268s (process:1999): libfprint-device-DEBUG: 17:02:26.742: Device reported close completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.742: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.742: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 268s ok 268s test_delete_print (__main__.VirtualDeviceBusyDeviceOperations.test_delete_print) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.742: 102727701: ../libfprint/drivers/virtual-device.c:387 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.742: 102727710: ../libfprint/drivers/virtual-device-listener.c:153 268s (process:1999): libfprint-device-DEBUG: 17:02:26.742: Device reported open completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.742: Completing action FPI_DEVICE_ACTION_OPEN in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.742: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.743: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.743: Got instructions of length 9 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.743: Received command SLEEP 200 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.743: Processing command SLEEP 200 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.743: Sleeping 200ms 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.943: Sleeping completed 268s (process:1999): libfprint-device-DEBUG: 17:02:26.943: Device reported close completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.943: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.943: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 268s ok 268s test_enroll (__main__.VirtualDeviceBusyDeviceOperations.test_enroll) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.943: 102928784: ../libfprint/drivers/virtual-device.c:387 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.943: 102928793: ../libfprint/drivers/virtual-device-listener.c:153 268s (process:1999): libfprint-device-DEBUG: 17:02:26.943: Device reported open completion 268s (process:1999): libfprint-device-DEBUG: 17:02:26.944: Completing action FPI_DEVICE_ACTION_OPEN in idle! 268s (process:1999): libfprint-device-DEBUG: 17:02:26.944: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 268s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:26.944: Got a new connection! 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.944: Got instructions of length 9 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.944: Received command SLEEP 200 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.944: Processing command SLEEP 200 268s (process:1999): libfprint-virtual_device-DEBUG: 17:02:26.944: Sleeping 200ms 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.144: Sleeping completed 269s (process:1999): libfprint-device-DEBUG: 17:02:27.144: Device reported close completion 269s (process:1999): libfprint-device-DEBUG: 17:02:27.144: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 269s (process:1999): libfprint-device-DEBUG: 17:02:27.144: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 269s ok 269s test_identify (__main__.VirtualDeviceBusyDeviceOperations.test_identify) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.144: 103129857: ../libfprint/drivers/virtual-device.c:387 269s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:27.144: 103129866: ../libfprint/drivers/virtual-device-listener.c:153 269s (process:1999): libfprint-device-DEBUG: 17:02:27.145: Device reported open completion 269s (process:1999): libfprint-device-DEBUG: 17:02:27.145: Completing action FPI_DEVICE_ACTION_OPEN in idle! 269s (process:1999): libfprint-device-DEBUG: 17:02:27.145: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 269s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:27.145: Got a new connection! 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.145: Got instructions of length 9 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.145: Received command SLEEP 200 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.145: Processing command SLEEP 200 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.145: Sleeping 200ms 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.345: Sleeping completed 269s (process:1999): libfprint-device-DEBUG: 17:02:27.345: Device reported close completion 269s (process:1999): libfprint-device-DEBUG: 17:02:27.345: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 269s (process:1999): libfprint-device-DEBUG: 17:02:27.345: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 269s ok 269s test_list_prints (__main__.VirtualDeviceBusyDeviceOperations.test_list_prints) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.346: 103330939: ../libfprint/drivers/virtual-device.c:387 269s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:27.346: 103330948: ../libfprint/drivers/virtual-device-listener.c:153 269s (process:1999): libfprint-device-DEBUG: 17:02:27.346: Device reported open completion 269s (process:1999): libfprint-device-DEBUG: 17:02:27.346: Completing action FPI_DEVICE_ACTION_OPEN in idle! 269s (process:1999): libfprint-device-DEBUG: 17:02:27.346: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 269s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:27.346: Got a new connection! 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.346: Got instructions of length 9 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.346: Received command SLEEP 200 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.346: Processing command SLEEP 200 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.346: Sleeping 200ms 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.546: Sleeping completed 269s (process:1999): libfprint-device-DEBUG: 17:02:27.546: Device reported close completion 269s (process:1999): libfprint-device-DEBUG: 17:02:27.546: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 269s (process:1999): libfprint-device-DEBUG: 17:02:27.547: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 269s ok 269s test_open (__main__.VirtualDeviceBusyDeviceOperations.test_open) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.547: 103532059: ../libfprint/drivers/virtual-device.c:387 269s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:27.547: 103532069: ../libfprint/drivers/virtual-device-listener.c:153 269s (process:1999): libfprint-device-DEBUG: 17:02:27.547: Device reported open completion 269s (process:1999): libfprint-device-DEBUG: 17:02:27.547: Completing action FPI_DEVICE_ACTION_OPEN in idle! 269s (process:1999): libfprint-device-DEBUG: 17:02:27.547: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 269s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:27.547: Got a new connection! 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.547: Got instructions of length 9 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.547: Received command SLEEP 200 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.547: Processing command SLEEP 200 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.547: Sleeping 200ms 269s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:27.547: Got a new connection! 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.547: Got instructions of length 16 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.547: Received command SET_KEEP_ALIVE 1 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.547: Keep alive toggled: 1 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.747: Sleeping completed 269s (process:1999): libfprint-device-DEBUG: 17:02:27.747: Device reported close completion 269s (process:1999): libfprint-device-DEBUG: 17:02:27.748: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 269s (process:1999): libfprint-device-DEBUG: 17:02:27.748: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 269s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:27.748: Got a new connection! 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.748: Got instructions of length 9 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.748: Received command SLEEP 100 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.748: 103733164: ../libfprint/drivers/virtual-device.c:387 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.748: Processing command SLEEP 100 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.748: Sleeping 100ms 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.848: Sleeping completed 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.848: 103833553: ../libfprint/drivers/virtual-device.c:387 269s (process:1999): libfprint-device-DEBUG: 17:02:27.848: Device reported open completion 269s (process:1999): libfprint-device-DEBUG: 17:02:27.848: Completing action FPI_DEVICE_ACTION_OPEN in idle! 269s (process:1999): libfprint-device-DEBUG: 17:02:27.848: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 269s (process:1999): libfprint-device-DEBUG: 17:02:27.848: Device reported close completion 269s (process:1999): libfprint-device-DEBUG: 17:02:27.848: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 269s (process:1999): libfprint-device-DEBUG: 17:02:27.848: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 269s ok 269s test_verify (__main__.VirtualDeviceBusyDeviceOperations.test_verify) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.848: 103833806: ../libfprint/drivers/virtual-device.c:387 269s (process:1999): libfprint-device-DEBUG: 17:02:27.848: Device reported open completion 269s (process:1999): libfprint-device-DEBUG: 17:02:27.848: Completing action FPI_DEVICE_ACTION_OPEN in idle! 269s (process:1999): libfprint-device-DEBUG: 17:02:27.848: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 269s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:27.849: Got a new connection! 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.849: Got instructions of length 9 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.849: Received command SLEEP 200 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.849: Processing command SLEEP 200 269s (process:1999): libfprint-virtual_device-DEBUG: 17:02:27.849: Sleeping 200ms 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.049: Sleeping completed 270s (process:1999): libfprint-device-DEBUG: 17:02:28.049: Device reported close completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.049: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.049: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.049: 104034832: ../libfprint/drivers/virtual-device.c:752 270s (process:1999): libfprint-context-DEBUG: 17:02:28.050: Initializing FpContext (libfprint version 1.94.7+tod1) 270s (process:1999): libfprint-tod-DEBUG: 17:02:28.050: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 270s (process:1999): libfprint-context-DEBUG: 17:02:28.050: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-1djc49dz/virtual-device.socket 270s (process:1999): libfprint-context-DEBUG: 17:02:28.050: created 270s (process:1999): libfprint-device-DEBUG: 17:02:28.051: Device reported probe completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.051: Completing action FPI_DEVICE_ACTION_PROBE in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.051: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s test_capture (__main__.VirtualDeviceClosed.test_capture) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.051: 104036296: ../libfprint/drivers/virtual-device.c:387 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.051: 104036305: ../libfprint/drivers/virtual-device-listener.c:153 270s (process:1999): libfprint-device-DEBUG: 17:02:28.051: Device reported open completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.051: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.051: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s (process:1999): libfprint-device-DEBUG: 17:02:28.051: Device reported close completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.051: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.051: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 270s test_close (__main__.VirtualDeviceClosed.test_close) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.051: 104036582: ../libfprint/drivers/virtual-device.c:387 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.051: 104036589: ../libfprint/drivers/virtual-device-listener.c:153 270s (process:1999): libfprint-device-DEBUG: 17:02:28.051: Device reported open completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.051: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.051: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s (process:1999): libfprint-device-DEBUG: 17:02:28.051: Device reported close completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.051: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.051: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 270s test_delete_print (__main__.VirtualDeviceClosed.test_delete_print) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.051: 104036787: ../libfprint/drivers/virtual-device.c:387 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.051: 104036793: ../libfprint/drivers/virtual-device-listener.c:153 270s (process:1999): libfprint-device-DEBUG: 17:02:28.051: Device reported open completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.051: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.051: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s (process:1999): libfprint-device-DEBUG: 17:02:28.051: Device reported close completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.051: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.051: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 270s test_enroll (__main__.VirtualDeviceClosed.test_enroll) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.052: 104036989: ../libfprint/drivers/virtual-device.c:387 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.052: 104036995: ../libfprint/drivers/virtual-device-listener.c:153 270s (process:1999): libfprint-device-DEBUG: 17:02:28.052: Device reported open completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.052: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.052: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s (process:1999): libfprint-device-DEBUG: 17:02:28.052: Device reported close completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.052: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.052: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 270s test_identify (__main__.VirtualDeviceClosed.test_identify) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.052: 104037190: ../libfprint/drivers/virtual-device.c:387 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.052: 104037197: ../libfprint/drivers/virtual-device-listener.c:153 270s (process:1999): libfprint-device-DEBUG: 17:02:28.052: Device reported open completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.052: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.052: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s (process:1999): libfprint-device-DEBUG: 17:02:28.052: Device reported close completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.052: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.052: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 270s test_list_prints (__main__.VirtualDeviceClosed.test_list_prints) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.052: 104037415: ../libfprint/drivers/virtual-device.c:387 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.052: 104037422: ../libfprint/drivers/virtual-device-listener.c:153 270s (process:1999): libfprint-device-DEBUG: 17:02:28.052: Device reported open completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.052: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.052: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s (process:1999): libfprint-device-DEBUG: 17:02:28.052: Device reported close completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.052: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.052: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 270s test_verify (__main__.VirtualDeviceClosed.test_verify) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.052: 104037608: ../libfprint/drivers/virtual-device.c:387 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.052: 104037613: ../libfprint/drivers/virtual-device-listener.c:153 270s (process:1999): libfprint-device-DEBUG: 17:02:28.052: Device reported open completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.052: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.052: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s (process:1999): libfprint-device-DEBUG: 17:02:28.052: Device reported close completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.052: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.052: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.052: 104037892: ../libfprint/drivers/virtual-device.c:752 270s (process:1999): libfprint-context-DEBUG: 17:02:28.053: Initializing FpContext (libfprint version 1.94.7+tod1) 270s (process:1999): libfprint-tod-DEBUG: 17:02:28.053: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 270s (process:1999): libfprint-context-DEBUG: 17:02:28.053: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-1djc49dz/virtual-device.socket 270s (process:1999): libfprint-context-DEBUG: 17:02:28.053: created 270s (process:1999): libfprint-context-DEBUG: 17:02:28.053: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-pqcq12qf/virtual-device-storage.socket 270s (process:1999): libfprint-context-DEBUG: 17:02:28.053: created 270s (process:1999): libfprint-device-DEBUG: 17:02:28.054: Device reported probe completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.054: Device reported probe completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.054: Completing action FPI_DEVICE_ACTION_PROBE in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.054: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s (process:1999): libfprint-device-DEBUG: 17:02:28.054: Completing action FPI_DEVICE_ACTION_PROBE in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.054: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s test_capture_unsupported (__main__.VirtualDeviceStorage.test_capture_unsupported) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.054: 104039411: ../libfprint/drivers/virtual-device.c:387 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.054: 104039420: ../libfprint/drivers/virtual-device-listener.c:153 270s (process:1999): libfprint-device-DEBUG: 17:02:28.054: Device reported open completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.054: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.054: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.054: Got a new connection! 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.054: Got instructions of length 5 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.054: Received command CONT 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.054: Processing command CONT 270s (process:1999): libfprint-device-DEBUG: 17:02:28.054: Device reported deletion completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.054: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.054: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.054: Got a new connection! 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.054: Got instructions of length 16 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.054: Received command SET_KEEP_ALIVE 0 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.054: Keep alive toggled: 0 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.054: Got a new connection! 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.055: Got instructions of length 19 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.055: Received command SET_ENROLL_STAGES 5 270s (process:1999): libfprint-device-DEBUG: 17:02:28.055: Device reported close completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.055: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.055: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 270s test_change_enroll_stages (__main__.VirtualDeviceStorage.test_change_enroll_stages) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.055: 104040138: ../libfprint/drivers/virtual-device.c:387 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.055: 104040341: ../libfprint/drivers/virtual-device-listener.c:153 270s (process:1999): libfprint-device-DEBUG: 17:02:28.055: Device reported open completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.055: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.055: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.055: Got a new connection! 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.055: Got instructions of length 20 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.055: Received command SET_ENROLL_STAGES 20 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.055: Got a new connection! 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.055: Got instructions of length 19 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.055: Received command SET_ENROLL_STAGES 1 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.055: Got a new connection! 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.055: Got instructions of length 19 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.055: Received command SET_ENROLL_STAGES 0 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.056: Got a new connection! 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.056: Got instructions of length 5 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.056: Received command CONT 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.056: Processing command CONT 270s (process:1999): libfprint-device-DEBUG: 17:02:28.056: Device reported deletion completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.056: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.056: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.056: Got a new connection! 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.056: Got instructions of length 16 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.056: Received command SET_KEEP_ALIVE 0 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.056: Keep alive toggled: 0 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.056: Got a new connection! 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.056: Got instructions of length 19 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.056: Received command SET_ENROLL_STAGES 5 270s (process:1999): libfprint-device-DEBUG: 17:02:28.056: Device reported close completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.056: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.056: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 270s test_change_scan_type (__main__.VirtualDeviceStorage.test_change_scan_type) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.056: 104041311: ../libfprint/drivers/virtual-device.c:387 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.056: 104041318: ../libfprint/drivers/virtual-device-listener.c:153 270s (process:1999): libfprint-device-DEBUG: 17:02:28.056: Device reported open completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.056: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.056: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.056: Got a new connection! 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.056: Got instructions of length 19 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.056: Received command SET_SCAN_TYPE press 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.056: Got a new connection! 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.056: Got instructions of length 19 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.056: Received command SET_SCAN_TYPE swipe 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.056: Got a new connection! 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.056: Got instructions of length 25 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.056: Received command SET_SCAN_TYPE eye-contact 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.056: Got a new connection! 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.057: Got instructions of length 5 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.057: Received command CONT 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.057: Processing command CONT 270s (process:1999): libfprint-device-DEBUG: 17:02:28.057: Device reported deletion completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.057: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.057: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.057: Got a new connection! 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.057: Got instructions of length 16 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.057: Received command SET_KEEP_ALIVE 0 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.057: Keep alive toggled: 0 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.057: Got a new connection! 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.057: Got instructions of length 19 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.057: Received command SET_ENROLL_STAGES 5 270s (process:1999): libfprint-device-DEBUG: 17:02:28.057: Device reported close completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.057: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.057: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 270s test_clear_storage (__main__.VirtualDeviceStorage.test_clear_storage) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.057: 104042203: ../libfprint/drivers/virtual-device.c:387 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.057: 104042209: ../libfprint/drivers/virtual-device-listener.c:153 270s (process:1999): libfprint-device-DEBUG: 17:02:28.057: Device reported open completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.057: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.057: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.057: Got a new connection! 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.057: Got instructions of length 9 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.057: Received command INSERT p1 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.057: Processing command INSERT p1 270s (process:1999): libfprint-device-DEBUG: 17:02:28.558: Device reported listing completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.558: Completing action FPI_DEVICE_ACTION_LIST in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.558: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:28.558: Got a new connection! 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.558: Got instructions of length 5 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.558: Received command CONT 270s (process:1999): libfprint-virtual_device-DEBUG: 17:02:28.558: Processing command CONT 270s (process:1999): libfprint-device-DEBUG: 17:02:28.558: Device reported deletion completion 270s (process:1999): libfprint-device-DEBUG: 17:02:28.558: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 270s (process:1999): libfprint-device-DEBUG: 17:02:28.558: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 271s (process:1999): libfprint-device-DEBUG: 17:02:29.059: Device reported listing completion 271s (process:1999): libfprint-device-DEBUG: 17:02:29.059: Completing action FPI_DEVICE_ACTION_LIST in idle! 271s (process:1999): libfprint-device-DEBUG: 17:02:29.059: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 271s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:29.059: Got a new connection! 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.059: Got instructions of length 5 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.059: Received command CONT 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.059: Processing command CONT 271s (process:1999): libfprint-device-DEBUG: 17:02:29.059: Device reported deletion completion 271s (process:1999): libfprint-device-DEBUG: 17:02:29.059: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 271s (process:1999): libfprint-device-DEBUG: 17:02:29.059: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 271s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:29.059: Got a new connection! 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.059: Got instructions of length 16 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.059: Received command SET_KEEP_ALIVE 0 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.059: Keep alive toggled: 0 271s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:29.059: Got a new connection! 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.059: Got instructions of length 19 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.059: Received command SET_ENROLL_STAGES 5 271s (process:1999): libfprint-device-DEBUG: 17:02:29.059: Device reported close completion 271s (process:1999): libfprint-device-DEBUG: 17:02:29.059: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 271s (process:1999): libfprint-device-DEBUG: 17:02:29.059: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 271s 271s ok 271s test_clear_storage_error (__main__.VirtualDeviceStorage.test_clear_storage_error) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.059: 105044704: ../libfprint/drivers/virtual-device.c:387 271s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:29.059: 105044711: ../libfprint/drivers/virtual-device-listener.c:153 271s (process:1999): libfprint-device-DEBUG: 17:02:29.059: Device reported open completion 271s (process:1999): libfprint-device-DEBUG: 17:02:29.059: Completing action FPI_DEVICE_ACTION_OPEN in idle! 271s (process:1999): libfprint-device-DEBUG: 17:02:29.059: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 271s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:29.059: Got a new connection! 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.060: Got instructions of length 9 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.060: Received command INSERT p1 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.060: Processing command INSERT p1 271s (process:1999): libfprint-device-DEBUG: 17:02:29.560: Device reported listing completion 271s (process:1999): libfprint-device-DEBUG: 17:02:29.560: Completing action FPI_DEVICE_ACTION_LIST in idle! 271s (process:1999): libfprint-device-DEBUG: 17:02:29.560: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 271s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:29.560: Got a new connection! 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.560: Got instructions of length 7 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.560: Received command ERROR 5 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.560: Processing command ERROR 5 271s (process:1999): libfprint-device-DEBUG: 17:02:29.560: Device reported deletion completion 271s (process:1999): libfprint-device-DEBUG: 17:02:29.561: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 271s (process:1999): libfprint-device-DEBUG: 17:02:29.561: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 271s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:29.561: Got a new connection! 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.561: Got instructions of length 5 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.561: Received command CONT 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.561: Processing command CONT 271s (process:1999): libfprint-device-DEBUG: 17:02:29.561: Device reported deletion completion 271s (process:1999): libfprint-device-DEBUG: 17:02:29.561: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 271s (process:1999): libfprint-device-DEBUG: 17:02:29.561: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 271s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:29.561: Got a new connection! 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.561: Got instructions of length 16 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.561: Received command SET_KEEP_ALIVE 0 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.561: Keep alive toggled: 0 271s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:29.561: Got a new connection! 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.561: Got instructions of length 19 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.561: Received command SET_ENROLL_STAGES 5 271s (process:1999): libfprint-device-DEBUG: 17:02:29.561: Device reported close completion 271s (process:1999): libfprint-device-DEBUG: 17:02:29.561: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 271s (process:1999): libfprint-device-DEBUG: 17:02:29.561: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 271s 271s ok 271s test_close_error (__main__.VirtualDeviceStorage.test_close_error) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.561: 105546401: ../libfprint/drivers/virtual-device.c:387 271s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:29.561: 105546408: ../libfprint/drivers/virtual-device-listener.c:153 271s (process:1999): libfprint-device-DEBUG: 17:02:29.561: Device reported open completion 271s (process:1999): libfprint-device-DEBUG: 17:02:29.561: Completing action FPI_DEVICE_ACTION_OPEN in idle! 271s (process:1999): libfprint-device-DEBUG: 17:02:29.561: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 271s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:29.561: Got a new connection! 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.561: Got instructions of length 9 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.561: Received command SLEEP 100 271s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:29.561: Got a new connection! 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.561: Got instructions of length 7 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.561: Received command ERROR 4 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.561: Processing command SLEEP 100 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.561: Sleeping 100ms 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.662: Sleeping completed 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.662: Processing command ERROR 4 271s (process:1999): libfprint-device-DEBUG: 17:02:29.662: Device reported close completion 271s (process:1999): libfprint-device-DEBUG: 17:02:29.662: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 271s (process:1999): libfprint-device-DEBUG: 17:02:29.662: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 271s ok 271s test_close_while_opening (__main__.VirtualDeviceStorage.test_close_while_opening) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.662: 105647538: ../libfprint/drivers/virtual-device.c:387 271s (process:1999): libfprint-device-DEBUG: 17:02:29.662: Device reported open completion 271s (process:1999): libfprint-device-DEBUG: 17:02:29.662: Completing action FPI_DEVICE_ACTION_OPEN in idle! 271s (process:1999): libfprint-device-DEBUG: 17:02:29.662: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 271s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:29.662: Got a new connection! 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.663: Got instructions of length 16 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.663: Received command SET_KEEP_ALIVE 1 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.663: Keep alive toggled: 1 271s (process:1999): libfprint-device-DEBUG: 17:02:29.663: Device reported close completion 271s (process:1999): libfprint-device-DEBUG: 17:02:29.663: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 271s (process:1999): libfprint-device-DEBUG: 17:02:29.663: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 271s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:29.663: Got a new connection! 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.663: Got instructions of length 9 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.663: Received command SLEEP 500 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.663: 105648518: ../libfprint/drivers/virtual-device.c:387 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.663: Processing command SLEEP 500 271s (process:1999): libfprint-virtual_device-DEBUG: 17:02:29.663: Sleeping 500ms 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.164: Sleeping completed 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.164: 106149378: ../libfprint/drivers/virtual-device.c:387 272s (process:1999): libfprint-device-DEBUG: 17:02:30.164: Device reported open completion 272s (process:1999): libfprint-device-DEBUG: 17:02:30.164: Completing action FPI_DEVICE_ACTION_OPEN in idle! 272s (process:1999): libfprint-device-DEBUG: 17:02:30.164: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 272s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:30.164: Got a new connection! 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.165: Got instructions of length 5 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.165: Received command CONT 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.165: Processing command CONT 272s (process:1999): libfprint-device-DEBUG: 17:02:30.165: Device reported deletion completion 272s (process:1999): libfprint-device-DEBUG: 17:02:30.165: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 272s (process:1999): libfprint-device-DEBUG: 17:02:30.165: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 272s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:30.165: Got a new connection! 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.165: Got instructions of length 16 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.165: Received command SET_KEEP_ALIVE 0 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.165: Keep alive toggled: 0 272s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:30.165: Got a new connection! 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.165: Got instructions of length 19 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.165: Received command SET_ENROLL_STAGES 5 272s (process:1999): libfprint-device-DEBUG: 17:02:30.165: Device reported close completion 272s (process:1999): libfprint-device-DEBUG: 17:02:30.165: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 272s (process:1999): libfprint-device-DEBUG: 17:02:30.166: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 272s ok 272s test_delayed_open (__main__.VirtualDeviceStorage.test_delayed_open) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.166: 106151108: ../libfprint/drivers/virtual-device.c:387 272s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:30.166: 106151150: ../libfprint/drivers/virtual-device-listener.c:153 272s (process:1999): libfprint-device-DEBUG: 17:02:30.166: Device reported open completion 272s (process:1999): libfprint-device-DEBUG: 17:02:30.166: Completing action FPI_DEVICE_ACTION_OPEN in idle! 272s (process:1999): libfprint-device-DEBUG: 17:02:30.166: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 272s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:30.166: Got a new connection! 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.166: Got instructions of length 16 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.166: Received command IGNORED_COMMAND 272s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:30.166: Got a new connection! 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.166: Got instructions of length 9 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.166: Received command SLEEP 500 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.167: Processing command IGNORED_COMMAND 272s (process:1999): libfprint-device-DEBUG: 17:02:30.167: Device reported close completion 272s (process:1999): libfprint-device-DEBUG: 17:02:30.167: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 272s (process:1999): libfprint-device-DEBUG: 17:02:30.167: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.167: 106152274: ../libfprint/drivers/virtual-device.c:387 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.167: Processing command SLEEP 500 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.167: Sleeping 500ms 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.668: Sleeping completed 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.668: 106653092: ../libfprint/drivers/virtual-device.c:387 272s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:30.668: 106653109: ../libfprint/drivers/virtual-device-listener.c:153 272s (process:1999): libfprint-device-DEBUG: 17:02:30.668: Device reported open completion 272s (process:1999): libfprint-device-DEBUG: 17:02:30.668: Completing action FPI_DEVICE_ACTION_OPEN in idle! 272s (process:1999): libfprint-device-DEBUG: 17:02:30.668: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 272s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:30.668: Got a new connection! 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.668: Got instructions of length 5 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.668: Received command CONT 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.668: Processing command CONT 272s (process:1999): libfprint-device-DEBUG: 17:02:30.668: Device reported deletion completion 272s (process:1999): libfprint-device-DEBUG: 17:02:30.668: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 272s (process:1999): libfprint-device-DEBUG: 17:02:30.668: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 272s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:30.668: Got a new connection! 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.668: Got instructions of length 16 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.668: Received command SET_KEEP_ALIVE 0 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.668: Keep alive toggled: 0 272s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:30.668: Got a new connection! 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.668: Got instructions of length 19 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.668: Received command SET_ENROLL_STAGES 5 272s (process:1999): libfprint-device-DEBUG: 17:02:30.668: Device reported close completion 272s (process:1999): libfprint-device-DEBUG: 17:02:30.668: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 272s (process:1999): libfprint-device-DEBUG: 17:02:30.668: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 272s ok 272s test_delayed_open_with_keep_alive (__main__.VirtualDeviceStorage.test_delayed_open_with_keep_alive) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.669: 106653929: ../libfprint/drivers/virtual-device.c:387 272s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:30.669: 106653935: ../libfprint/drivers/virtual-device-listener.c:153 272s (process:1999): libfprint-device-DEBUG: 17:02:30.669: Device reported open completion 272s (process:1999): libfprint-device-DEBUG: 17:02:30.669: Completing action FPI_DEVICE_ACTION_OPEN in idle! 272s (process:1999): libfprint-device-DEBUG: 17:02:30.669: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 272s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:30.669: Got a new connection! 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.669: Got instructions of length 16 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.669: Received command SET_KEEP_ALIVE 1 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.669: Keep alive toggled: 1 272s (process:1999): libfprint-device-DEBUG: 17:02:30.669: Device reported close completion 272s (process:1999): libfprint-device-DEBUG: 17:02:30.669: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 272s (process:1999): libfprint-device-DEBUG: 17:02:30.669: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 272s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:30.669: Got a new connection! 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.669: Got instructions of length 9 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.669: Received command SLEEP 500 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.669: 106654283: ../libfprint/drivers/virtual-device.c:387 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.669: Processing command SLEEP 500 272s (process:1999): libfprint-virtual_device-DEBUG: 17:02:30.669: Sleeping 500ms 273s Executing: libfprint-2/virtual-device.test 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.169: Sleeping completed 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.170: 107155044: ../libfprint/drivers/virtual-device.c:387 273s (process:1999): libfprint-device-DEBUG: 17:02:31.170: Device reported open completion 273s (process:1999): libfprint-device-DEBUG: 17:02:31.170: Completing action FPI_DEVICE_ACTION_OPEN in idle! 273s (process:1999): libfprint-device-DEBUG: 17:02:31.170: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 273s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:31.170: Got a new connection! 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.170: Got instructions of length 5 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.170: Received command CONT 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.170: Processing command CONT 273s (process:1999): libfprint-device-DEBUG: 17:02:31.170: Device reported deletion completion 273s (process:1999): libfprint-device-DEBUG: 17:02:31.170: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 273s (process:1999): libfprint-device-DEBUG: 17:02:31.171: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 273s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:31.171: Got a new connection! 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.171: Got instructions of length 16 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.171: Received command SET_KEEP_ALIVE 0 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.171: Keep alive toggled: 0 273s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:31.171: Got a new connection! 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.171: Got instructions of length 19 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.171: Received command SET_ENROLL_STAGES 5 273s (process:1999): libfprint-device-DEBUG: 17:02:31.171: Device reported close completion 273s (process:1999): libfprint-device-DEBUG: 17:02:31.171: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 273s (process:1999): libfprint-device-DEBUG: 17:02:31.171: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 273s ok 273s test_delete_error (__main__.VirtualDeviceStorage.test_delete_error) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.171: 107156785: ../libfprint/drivers/virtual-device.c:387 273s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:31.171: 107156799: ../libfprint/drivers/virtual-device-listener.c:153 273s (process:1999): libfprint-device-DEBUG: 17:02:31.171: Device reported open completion 273s (process:1999): libfprint-device-DEBUG: 17:02:31.172: Completing action FPI_DEVICE_ACTION_OPEN in idle! 273s (process:1999): libfprint-device-DEBUG: 17:02:31.172: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 273s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:31.172: Got a new connection! 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.172: Got instructions of length 9 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.172: Received command SLEEP 100 273s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:31.172: Got a new connection! 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.172: Got instructions of length 7 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.172: Received command ERROR 7 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.172: Processing command SLEEP 100 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.172: Sleeping 100ms 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.272: Sleeping completed 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.272: Processing command ERROR 7 273s (process:1999): libfprint-device-DEBUG: 17:02:31.272: Device reported deletion completion 273s (process:1999): libfprint-device-DEBUG: 17:02:31.272: Completing action FPI_DEVICE_ACTION_DELETE in idle! 273s (process:1999): libfprint-device-DEBUG: 17:02:31.272: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 273s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:31.273: Got a new connection! 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.273: Got instructions of length 5 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.273: Received command CONT 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.273: Processing command CONT 273s (process:1999): libfprint-device-DEBUG: 17:02:31.273: Device reported deletion completion 273s (process:1999): libfprint-device-DEBUG: 17:02:31.273: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 273s (process:1999): libfprint-device-DEBUG: 17:02:31.273: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 273s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:31.273: Got a new connection! 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.273: Got instructions of length 16 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.273: Received command SET_KEEP_ALIVE 0 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.273: Keep alive toggled: 0 273s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:31.273: Got a new connection! 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.273: Got instructions of length 19 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.273: Received command SET_ENROLL_STAGES 5 273s (process:1999): libfprint-device-DEBUG: 17:02:31.273: Device reported close completion 273s (process:1999): libfprint-device-DEBUG: 17:02:31.273: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 273s (process:1999): libfprint-device-DEBUG: 17:02:31.273: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 273s ok 273s test_delete_multiple_times (__main__.VirtualDeviceStorage.test_delete_multiple_times) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.273: 107258431: ../libfprint/drivers/virtual-device.c:387 273s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:31.273: 107258442: ../libfprint/drivers/virtual-device-listener.c:153 273s (process:1999): libfprint-device-DEBUG: 17:02:31.273: Device reported open completion 273s (process:1999): libfprint-device-DEBUG: 17:02:31.273: Completing action FPI_DEVICE_ACTION_OPEN in idle! 273s (process:1999): libfprint-device-DEBUG: 17:02:31.273: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 273s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:31.273: Got a new connection! 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.273: Got instructions of length 16 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.273: Received command SCAN right-thumb 273s (process:1999): libfprint-device-DEBUG: 17:02:31.273: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.273: Processing command SCAN right-thumb 273s (process:1999): libfprint-device-DEBUG: 17:02:31.273: Device reported finger status change: FP_FINGER_STATUS_NEEDED 273s (process:1999): libfprint-device-DEBUG: 17:02:31.273: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 273s (process:1999): libfprint-device-DEBUG: 17:02:31.273: Device reported finger status change: FP_FINGER_STATUS_NEEDED 273s (process:1999): libfprint-device-DEBUG: 17:02:31.273: Device reported enroll progress, reported 1 of 5 have been completed 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.273: Sleeping completed 273s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:31.273: Got a new connection! 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.274: Got instructions of length 16 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.274: Received command SCAN right-thumb 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.274: Processing command SCAN right-thumb 273s (process:1999): libfprint-device-DEBUG: 17:02:31.274: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 273s (process:1999): libfprint-device-DEBUG: 17:02:31.274: Device reported finger status change: FP_FINGER_STATUS_NEEDED 273s (process:1999): libfprint-device-DEBUG: 17:02:31.274: Device reported enroll progress, reported 2 of 5 have been completed 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.274: Sleeping completed 273s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:31.274: Got a new connection! 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.274: Got instructions of length 16 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.274: Received command SCAN right-thumb 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.274: Processing command SCAN right-thumb 273s (process:1999): libfprint-device-DEBUG: 17:02:31.274: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 273s (process:1999): libfprint-device-DEBUG: 17:02:31.274: Device reported finger status change: FP_FINGER_STATUS_NEEDED 273s (process:1999): libfprint-device-DEBUG: 17:02:31.274: Device reported enroll progress, reported 3 of 5 have been completed 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.274: Sleeping completed 273s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:31.274: Got a new connection! 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.274: Got instructions of length 16 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.274: Received command SCAN right-thumb 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.274: Processing command SCAN right-thumb 273s (process:1999): libfprint-device-DEBUG: 17:02:31.274: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 273s (process:1999): libfprint-device-DEBUG: 17:02:31.274: Device reported finger status change: FP_FINGER_STATUS_NEEDED 273s (process:1999): libfprint-device-DEBUG: 17:02:31.274: Device reported enroll progress, reported 4 of 5 have been completed 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.274: Sleeping completed 273s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:31.274: Got a new connection! 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.274: Got instructions of length 16 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.274: Received command SCAN right-thumb 273s (process:1999): libfprint-virtual_device-DEBUG: 17:02:31.274: Processing command SCAN right-thumb 273s (process:1999): libfprint-device-DEBUG: 17:02:31.274: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 273s (process:1999): libfprint-device-DEBUG: 17:02:31.274: Device reported finger status change: FP_FINGER_STATUS_NEEDED 273s (process:1999): libfprint-device-DEBUG: 17:02:31.274: Device reported enroll progress, reported 5 of 5 have been completed 273s (process:1999): libfprint-device-DEBUG: 17:02:31.274: Device reported enroll completion 273s (process:1999): libfprint-device-DEBUG: 17:02:31.274: Device reported finger status change: FP_FINGER_STATUS_NONE 273s (process:1999): libfprint-device-DEBUG: 17:02:31.274: Print for finger FP_FINGER_RIGHT_THUMB enrolled 273s (process:1999): libfprint-device-DEBUG: 17:02:31.274: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 273s (process:1999): libfprint-device-DEBUG: 17:02:31.274: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 273s (process:1999): libfprint-virtual_device_storage-DEBUG: 17:02:31.775: Deleting print right-thumb for user testuser 273s (process:1999): libfprint-device-DEBUG: 17:02:31.775: Device reported deletion completion 273s (process:1999): libfprint-device-DEBUG: 17:02:31.775: Completing action FPI_DEVICE_ACTION_DELETE in idle! 273s (process:1999): libfprint-device-DEBUG: 17:02:31.775: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 274s (process:1999): libfprint-virtual_device_storage-DEBUG: 17:02:32.275: Deleting print right-thumb for user testuser 274s (process:1999): libfprint-device-DEBUG: 17:02:32.275: Device reported deletion completion 274s (process:1999): libfprint-device-DEBUG: 17:02:32.275: Completing action FPI_DEVICE_ACTION_DELETE in idle! 274s (process:1999): libfprint-device-DEBUG: 17:02:32.275: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 274s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:32.276: Got a new connection! 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.276: Got instructions of length 5 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.276: Received command CONT 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.276: Processing command CONT 274s (process:1999): libfprint-device-DEBUG: 17:02:32.276: Device reported deletion completion 274s (process:1999): libfprint-device-DEBUG: 17:02:32.276: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 274s (process:1999): libfprint-device-DEBUG: 17:02:32.276: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 274s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:32.276: Got a new connection! 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.276: Got instructions of length 16 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.276: Received command SET_KEEP_ALIVE 0 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.276: Keep alive toggled: 0 274s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:32.276: Got a new connection! 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.276: Got instructions of length 19 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.276: Received command SET_ENROLL_STAGES 5 274s (process:1999): libfprint-device-DEBUG: 17:02:32.276: Device reported close completion 274s (process:1999): libfprint-device-DEBUG: 17:02:32.276: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 274s (process:1999): libfprint-device-DEBUG: 17:02:32.276: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 274s Enroll done 274s ok 274s test_device_features (__main__.VirtualDeviceStorage.test_device_features) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.276: 108261555: ../libfprint/drivers/virtual-device.c:387 274s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:32.276: 108261562: ../libfprint/drivers/virtual-device-listener.c:153 274s (process:1999): libfprint-device-DEBUG: 17:02:32.276: Device reported open completion 274s (process:1999): libfprint-device-DEBUG: 17:02:32.276: Completing action FPI_DEVICE_ACTION_OPEN in idle! 274s (process:1999): libfprint-device-DEBUG: 17:02:32.276: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 274s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:32.276: Got a new connection! 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.276: Got instructions of length 5 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.276: Received command CONT 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.276: Processing command CONT 274s (process:1999): libfprint-device-DEBUG: 17:02:32.276: Device reported deletion completion 274s (process:1999): libfprint-device-DEBUG: 17:02:32.276: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 274s (process:1999): libfprint-device-DEBUG: 17:02:32.276: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 274s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:32.277: Got a new connection! 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.277: Got instructions of length 16 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.277: Received command SET_KEEP_ALIVE 0 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.277: Keep alive toggled: 0 274s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:32.277: Got a new connection! 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.277: Got instructions of length 19 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.277: Received command SET_ENROLL_STAGES 5 274s (process:1999): libfprint-device-DEBUG: 17:02:32.277: Device reported close completion 274s (process:1999): libfprint-device-DEBUG: 17:02:32.277: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 274s (process:1999): libfprint-device-DEBUG: 17:02:32.277: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 274s ok 274s test_device_properties (__main__.VirtualDeviceStorage.test_device_properties) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.277: 108262133: ../libfprint/drivers/virtual-device.c:387 274s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:32.277: 108262139: ../libfprint/drivers/virtual-device-listener.c:153 274s (process:1999): libfprint-device-DEBUG: 17:02:32.277: Device reported open completion 274s (process:1999): libfprint-device-DEBUG: 17:02:32.277: Completing action FPI_DEVICE_ACTION_OPEN in idle! 274s (process:1999): libfprint-device-DEBUG: 17:02:32.277: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 274s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:32.277: Got a new connection! 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.277: Got instructions of length 5 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.277: Received command CONT 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.277: Processing command CONT 274s (process:1999): libfprint-device-DEBUG: 17:02:32.277: Device reported deletion completion 274s (process:1999): libfprint-device-DEBUG: 17:02:32.277: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 274s (process:1999): libfprint-device-DEBUG: 17:02:32.277: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 274s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:32.277: Got a new connection! 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.277: Got instructions of length 16 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.277: Received command SET_KEEP_ALIVE 0 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.277: Keep alive toggled: 0 274s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:32.277: Got a new connection! 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.277: Got instructions of length 19 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.277: Received command SET_ENROLL_STAGES 5 274s (process:1999): libfprint-device-DEBUG: 17:02:32.277: Device reported close completion 274s (process:1999): libfprint-device-DEBUG: 17:02:32.277: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 274s (process:1999): libfprint-device-DEBUG: 17:02:32.277: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 274s ok 274s test_device_sleep (__main__.VirtualDeviceStorage.test_device_sleep) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.277: 108262641: ../libfprint/drivers/virtual-device.c:387 274s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:32.277: 108262647: ../libfprint/drivers/virtual-device-listener.c:153 274s (process:1999): libfprint-device-DEBUG: 17:02:32.277: Device reported open completion 274s (process:1999): libfprint-device-DEBUG: 17:02:32.277: Completing action FPI_DEVICE_ACTION_OPEN in idle! 274s (process:1999): libfprint-device-DEBUG: 17:02:32.277: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 274s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:32.277: Got a new connection! 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.277: Got instructions of length 10 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.277: Received command SLEEP 1500 274s (process:1999): libfprint-device-DEBUG: 17:02:32.278: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.278: Processing command SLEEP 1500 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.278: Sleeping 1500ms 274s (process:1999): libfprint-device-DEBUG: 17:02:32.578: Idle cancelling on ongoing operation! 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.578: Got cancellation! 274s (process:1999): libfprint-device-DEBUG: 17:02:32.578: Device reported finger status change: FP_FINGER_STATUS_NEEDED 274s (process:1999): libfprint-device-DEBUG: 17:02:32.578: Device reported identify completion 274s (process:1999): libfprint-device-DEBUG: 17:02:32.578: Device reported finger status change: FP_FINGER_STATUS_NONE 274s (process:1999): libfprint-device-DEBUG: 17:02:32.578: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 274s (process:1999): libfprint-device-DEBUG: 17:02:32.578: Updated temperature model after 0.30 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 274s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:32.778: Got a new connection! 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.778: Got instructions of length 5 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.778: Received command CONT 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.778: Processing command CONT 274s (process:1999): libfprint-device-DEBUG: 17:02:32.778: Device reported deletion completion 274s (process:1999): libfprint-device-DEBUG: 17:02:32.778: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 274s (process:1999): libfprint-device-DEBUG: 17:02:32.778: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 274s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:32.779: Got a new connection! 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.779: Got instructions of length 16 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.779: Received command SET_KEEP_ALIVE 0 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.779: Keep alive toggled: 0 274s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:32.779: Got a new connection! 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.779: Got instructions of length 19 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.779: Received command SET_ENROLL_STAGES 5 274s (process:1999): libfprint-device-DEBUG: 17:02:32.779: Device reported close completion 274s (process:1999): libfprint-device-DEBUG: 17:02:32.779: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 274s (process:1999): libfprint-device-DEBUG: 17:02:32.779: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 274s ok 274s test_device_sleep_before_completing_verify (__main__.VirtualDeviceStorage.test_device_sleep_before_completing_verify) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.780: 108764989: ../libfprint/drivers/virtual-device.c:387 274s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:32.780: 108765032: ../libfprint/drivers/virtual-device-listener.c:153 274s (process:1999): libfprint-device-DEBUG: 17:02:32.780: Device reported open completion 274s (process:1999): libfprint-device-DEBUG: 17:02:32.780: Completing action FPI_DEVICE_ACTION_OPEN in idle! 274s (process:1999): libfprint-device-DEBUG: 17:02:32.780: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 274s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:32.780: Got a new connection! 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.780: Got instructions of length 14 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.780: Received command SCAN foo-print 274s (process:1999): libfprint-device-DEBUG: 17:02:32.780: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.780: Processing command SCAN foo-print 274s (process:1999): libfprint-device-DEBUG: 17:02:32.780: Device reported finger status change: FP_FINGER_STATUS_NEEDED 274s (process:1999): libfprint-device-DEBUG: 17:02:32.780: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 274s (process:1999): libfprint-device-DEBUG: 17:02:32.780: Device reported finger status change: FP_FINGER_STATUS_NEEDED 274s (process:1999): libfprint-device-DEBUG: 17:02:32.780: Device reported enroll progress, reported 1 of 5 have been completed 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.781: Sleeping completed 274s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:32.781: Got a new connection! 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.781: Got instructions of length 14 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.781: Received command SCAN foo-print 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.781: Processing command SCAN foo-print 274s (process:1999): libfprint-device-DEBUG: 17:02:32.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 274s (process:1999): libfprint-device-DEBUG: 17:02:32.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED 274s (process:1999): libfprint-device-DEBUG: 17:02:32.781: Device reported enroll progress, reported 2 of 5 have been completed 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.781: Sleeping completed 274s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:32.781: Got a new connection! 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.781: Got instructions of length 14 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.781: Received command SCAN foo-print 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.781: Processing command SCAN foo-print 274s (process:1999): libfprint-device-DEBUG: 17:02:32.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 274s (process:1999): libfprint-device-DEBUG: 17:02:32.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED 274s (process:1999): libfprint-device-DEBUG: 17:02:32.781: Device reported enroll progress, reported 3 of 5 have been completed 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.781: Sleeping completed 274s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:32.782: Got a new connection! 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.782: Got instructions of length 14 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.782: Received command SCAN foo-print 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.782: Processing command SCAN foo-print 274s (process:1999): libfprint-device-DEBUG: 17:02:32.782: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 274s (process:1999): libfprint-device-DEBUG: 17:02:32.782: Device reported finger status change: FP_FINGER_STATUS_NEEDED 274s (process:1999): libfprint-device-DEBUG: 17:02:32.782: Device reported enroll progress, reported 4 of 5 have been completed 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.782: Sleeping completed 274s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:32.782: Got a new connection! 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.782: Got instructions of length 14 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.782: Received command SCAN foo-print 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.782: Processing command SCAN foo-print 274s (process:1999): libfprint-device-DEBUG: 17:02:32.782: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 274s (process:1999): libfprint-device-DEBUG: 17:02:32.782: Device reported finger status change: FP_FINGER_STATUS_NEEDED 274s (process:1999): libfprint-device-DEBUG: 17:02:32.782: Device reported enroll progress, reported 5 of 5 have been completed 274s (process:1999): libfprint-device-DEBUG: 17:02:32.782: Device reported enroll completion 274s (process:1999): libfprint-device-DEBUG: 17:02:32.782: Device reported finger status change: FP_FINGER_STATUS_NONE 274s (process:1999): libfprint-device-DEBUG: 17:02:32.782: Print for finger FP_FINGER_LEFT_RING enrolled 274s (process:1999): libfprint-device-DEBUG: 17:02:32.782: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 274s (process:1999): libfprint-device-DEBUG: 17:02:32.782: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 274s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:32.782: Got a new connection! 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.782: Got instructions of length 9 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.782: Received command SLEEP 100 274s (process:1999): libfprint-device-DEBUG: 17:02:32.782: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.782: Processing command SLEEP 100 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.782: Sleeping 100ms 274s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:32.782: Got a new connection! 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.782: Got instructions of length 14 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.782: Received command SCAN bar-print 274s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:32.782: Got a new connection! 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.782: Got instructions of length 9 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.782: Received command SLEEP 800 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.882: Sleeping completed 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.882: Processing command SCAN bar-print 274s (process:1999): libfprint-device-DEBUG: 17:02:32.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED 274s (process:1999): libfprint-device-DEBUG: 17:02:32.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 274s (process:1999): libfprint-virtual_device_storage-DEBUG: 17:02:32.883: Trying to identify print 'bar-print' against a gallery of 1 prints 274s (process:1999): libfprint-device-DEBUG: 17:02:32.883: Device reported identify result 274s (process:1999): libfprint-device-DEBUG: 17:02:32.883: Device reported finger status change: FP_FINGER_STATUS_NEEDED 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.883: Processing command SLEEP 800 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.883: Sleeping 800ms 274s (process:1999): libfprint-virtual_device-DEBUG: 17:02:32.883: Sleeping now, command queued for later: SCAN bar-print 275s (process:1999): libfprint-device-DEBUG: 17:02:33.119: Updated temperature model after 0.34 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 275s (process:1999): libfprint-virtual_device-DEBUG: 17:02:33.684: Sleeping completed 275s (process:1999): libfprint-virtual_device-DEBUG: 17:02:33.684: Processing command SCAN bar-print 275s (process:1999): libfprint-device-DEBUG: 17:02:33.684: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 275s (process:1999): libfprint-virtual_device_storage-DEBUG: 17:02:33.684: Trying to identify print 'bar-print' against a gallery of 1 prints 275s (process:1999): libfprint-device-DEBUG: 17:02:33.684: Device reported finger status change: FP_FINGER_STATUS_NEEDED 275s (process:1999): libfprint-device-DEBUG: 17:02:33.684: Device reported identify completion 275s (process:1999): libfprint-device-DEBUG: 17:02:33.684: Device reported finger status change: FP_FINGER_STATUS_NONE 275s (process:1999): libfprint-device-DEBUG: 17:02:33.684: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 275s (process:1999): libfprint-device-DEBUG: 17:02:33.684: Updated temperature model after 0.57 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 275s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:33.685: Got a new connection! 275s (process:1999): libfprint-virtual_device-DEBUG: 17:02:33.685: Got instructions of length 5 275s (process:1999): libfprint-virtual_device-DEBUG: 17:02:33.685: Received command CONT 275s (process:1999): libfprint-virtual_device-DEBUG: 17:02:33.685: Processing command CONT 275s (process:1999): libfprint-device-DEBUG: 17:02:33.685: Device reported deletion completion 275s (process:1999): libfprint-device-DEBUG: 17:02:33.685: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 275s (process:1999): libfprint-device-DEBUG: 17:02:33.685: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 275s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:33.685: Got a new connection! 275s (process:1999): libfprint-virtual_device-DEBUG: 17:02:33.685: Got instructions of length 16 275s (process:1999): libfprint-virtual_device-DEBUG: 17:02:33.685: Received command SET_KEEP_ALIVE 0 275s (process:1999): libfprint-virtual_device-DEBUG: 17:02:33.685: Keep alive toggled: 0 275s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:33.685: Got a new connection! 275s (process:1999): libfprint-virtual_device-DEBUG: 17:02:33.685: Got instructions of length 19 275s (process:1999): libfprint-virtual_device-DEBUG: 17:02:33.685: Received command SET_ENROLL_STAGES 5 275s (process:1999): libfprint-device-DEBUG: 17:02:33.686: Device reported close completion 275s (process:1999): libfprint-device-DEBUG: 17:02:33.686: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 275s (process:1999): libfprint-device-DEBUG: 17:02:33.686: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 275s Enroll done 275s ok 275s test_device_sleep_on_cancellation (__main__.VirtualDeviceStorage.test_device_sleep_on_cancellation) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:33.686: 109671235: ../libfprint/drivers/virtual-device.c:387 275s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:33.686: 109671278: ../libfprint/drivers/virtual-device-listener.c:153 275s (process:1999): libfprint-device-DEBUG: 17:02:33.686: Device reported open completion 275s (process:1999): libfprint-device-DEBUG: 17:02:33.686: Completing action FPI_DEVICE_ACTION_OPEN in idle! 275s (process:1999): libfprint-device-DEBUG: 17:02:33.686: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 275s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:33.686: Got a new connection! 275s (process:1999): libfprint-virtual_device-DEBUG: 17:02:33.686: Got instructions of length 26 275s (process:1999): libfprint-virtual_device-DEBUG: 17:02:33.686: Received command SET_CANCELLATION_ENABLED 0 275s (process:1999): libfprint-virtual_device-DEBUG: 17:02:33.686: Cancellation support toggled: 0 275s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:33.687: Got a new connection! 275s (process:1999): libfprint-virtual_device-DEBUG: 17:02:33.687: Got instructions of length 10 275s (process:1999): libfprint-virtual_device-DEBUG: 17:02:33.687: Received command SLEEP 1500 275s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:33.687: Got a new connection! 275s (process:1999): libfprint-virtual_device-DEBUG: 17:02:33.687: Got instructions of length 14 275s (process:1999): libfprint-virtual_device-DEBUG: 17:02:33.687: Received command SCAN foo-print 275s (process:1999): libfprint-device-DEBUG: 17:02:33.687: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 275s (process:1999): libfprint-virtual_device-DEBUG: 17:02:33.687: Processing command SLEEP 1500 275s (process:1999): libfprint-virtual_device-DEBUG: 17:02:33.687: Sleeping 1500ms 276s (process:1999): libfprint-device-DEBUG: 17:02:33.987: Idle cancelling on ongoing operation! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.188: Sleeping completed 277s (process:1999): libfprint-device-DEBUG: 17:02:35.188: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.188: Device reported identify completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.188: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.189: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.189: Updated temperature model after 1.50 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.189: Processing command SCAN foo-print 277s (process:1999): libfprint-device-DEBUG: 17:02:35.189: Device reported close completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.189: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.189: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s ok 277s test_duplicate_enroll (__main__.VirtualDeviceStorage.test_duplicate_enroll) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.189: 111174815: ../libfprint/drivers/virtual-device.c:387 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.189: 111174860: ../libfprint/drivers/virtual-device-listener.c:153 277s (process:1999): libfprint-device-DEBUG: 17:02:35.190: Device reported open completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.190: Completing action FPI_DEVICE_ACTION_OPEN in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.190: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.190: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.190: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.190: Received command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.190: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.190: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.190: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.190: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.190: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.190: Device reported enroll progress, reported 1 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.190: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.190: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.191: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.191: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.191: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.191: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.191: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.191: Device reported enroll progress, reported 2 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.191: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.191: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.191: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.191: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.191: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.191: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.191: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.191: Device reported enroll progress, reported 3 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.191: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.191: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.191: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.191: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.191: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.191: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.191: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.191: Device reported enroll progress, reported 4 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.191: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.192: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.192: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.192: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.192: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.192: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.192: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.192: Device reported enroll progress, reported 5 of 5 have been completed 277s (process:1999): libfprint-device-DEBUG: 17:02:35.192: Device reported enroll completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.192: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.192: Print for finger FP_FINGER_LEFT_LITTLE enrolled 277s (process:1999): libfprint-device-DEBUG: 17:02:35.192: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.192: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.192: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.192: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.192: Received command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.192: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.192: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.192: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.192: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.192: Device reported enroll completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.192: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.192: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.192: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.192: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.192: Got instructions of length 5 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.192: Received command CONT 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.192: Processing command CONT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.192: Device reported deletion completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.192: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.192: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.192: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.192: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.192: Received command SET_KEEP_ALIVE 0 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.192: Keep alive toggled: 0 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.192: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.192: Got instructions of length 19 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.192: Received command SET_ENROLL_STAGES 5 277s (process:1999): libfprint-device-DEBUG: 17:02:35.192: Device reported close completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.192: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.192: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s Enroll done 277s Enroll done 277s ok 277s test_enroll (__main__.VirtualDeviceStorage.test_enroll) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.192: 111177727: ../libfprint/drivers/virtual-device.c:387 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.192: 111177734: ../libfprint/drivers/virtual-device-listener.c:153 277s (process:1999): libfprint-device-DEBUG: 17:02:35.192: Device reported open completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.192: Completing action FPI_DEVICE_ACTION_OPEN in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.192: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.193: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.193: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.193: Received command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.193: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.193: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.193: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.193: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.193: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.193: Device reported enroll progress, reported 1 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.193: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.193: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.193: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.193: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.193: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.193: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.193: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.193: Device reported enroll progress, reported 2 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.193: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.193: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.193: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.193: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.193: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.193: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.193: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.193: Device reported enroll progress, reported 3 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.193: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.193: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.193: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.193: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.193: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.193: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.193: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.193: Device reported enroll progress, reported 4 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.193: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.193: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.193: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.193: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.193: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.193: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.193: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.193: Device reported enroll progress, reported 5 of 5 have been completed 277s (process:1999): libfprint-device-DEBUG: 17:02:35.193: Device reported enroll completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.193: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.193: Print for finger FP_FINGER_LEFT_LITTLE enrolled 277s (process:1999): libfprint-device-DEBUG: 17:02:35.193: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.193: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.193: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.193: Got instructions of length 5 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.193: Received command CONT 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.193: Processing command CONT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.193: Device reported deletion completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.193: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.193: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.193: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.193: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.193: Received command SET_KEEP_ALIVE 0 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.193: Keep alive toggled: 0 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.194: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.194: Got instructions of length 19 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.194: Received command SET_ENROLL_STAGES 5 277s (process:1999): libfprint-device-DEBUG: 17:02:35.194: Device reported close completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.194: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.194: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s Enroll done 277s ok 277s test_enroll_script (__main__.VirtualDeviceStorage.test_enroll_script) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.194: 111179047: ../libfprint/drivers/virtual-device.c:387 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.194: 111179053: ../libfprint/drivers/virtual-device-listener.c:153 277s (process:1999): libfprint-device-DEBUG: 17:02:35.194: Device reported open completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.194: Completing action FPI_DEVICE_ACTION_OPEN in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.194: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.194: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.194: Got instructions of length 19 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.194: Received command SET_ENROLL_STAGES 8 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.194: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.194: Got instructions of length 13 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.194: Received command SCAN print-id 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.194: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.194: Got instructions of length 13 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.194: Received command SCAN print-id 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.194: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.194: Got instructions of length 7 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.194: Received command RETRY 1 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.194: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.194: Got instructions of length 13 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.194: Received command SCAN print-id 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.194: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.194: Got instructions of length 7 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.194: Received command RETRY 3 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.194: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.194: Got instructions of length 13 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.194: Received command SCAN print-id 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.194: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.194: Got instructions of length 7 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.194: Received command RETRY 2 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.194: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.194: Got instructions of length 13 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.194: Received command SCAN print-id 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.194: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.194: Got instructions of length 8 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.194: Received command SLEEP 10 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.195: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.195: Got instructions of length 8 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.195: Received command SLEEP 20 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.195: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.195: Got instructions of length 7 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.195: Received command RETRY 0 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.195: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.195: Got instructions of length 7 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.195: Received command RETRY 3 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.195: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.195: Got instructions of length 13 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.195: Received command SCAN print-id 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.195: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.195: Got instructions of length 15 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.195: Received command SCAN another-id 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.196: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.196: Got instructions of length 13 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.196: Received command SCAN print-id 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.196: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.196: Got instructions of length 13 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.196: Received command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.196: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.196: Processing command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.196: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.196: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.196: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.196: Device reported enroll progress, reported 1 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.196: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.196: Processing command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.196: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.196: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.196: Device reported enroll progress, reported 2 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.196: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.196: Processing command RETRY 1 277s (process:1999): libfprint-device-DEBUG: 17:02:35.196: Device reported enroll progress, reported 2 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.196: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.197: Processing command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.197: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.197: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.197: Device reported enroll progress, reported 3 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.197: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.197: Processing command RETRY 3 277s (process:1999): libfprint-device-DEBUG: 17:02:35.197: Device reported enroll progress, reported 3 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.197: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.197: Processing command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.197: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.197: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.197: Device reported enroll progress, reported 4 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.197: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.197: Processing command RETRY 2 277s (process:1999): libfprint-device-DEBUG: 17:02:35.197: Device reported enroll progress, reported 4 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.197: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.197: Processing command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.197: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.197: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.197: Device reported enroll progress, reported 5 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.197: Processing command SLEEP 10 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.197: Sleeping 10ms 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.207: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.207: Processing command SLEEP 20 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.207: Sleeping 20ms 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.228: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.228: Processing command RETRY 0 277s (process:1999): libfprint-device-DEBUG: 17:02:35.228: Device reported enroll progress, reported 5 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.228: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.228: Processing command RETRY 3 277s (process:1999): libfprint-device-DEBUG: 17:02:35.228: Device reported enroll progress, reported 5 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.228: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.228: Processing command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.228: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.228: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.228: Device reported enroll progress, reported 6 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.228: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.228: Processing command SCAN another-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.228: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.228: Device reported enroll progress, reported 6 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.228: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.228: Processing command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.228: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.228: Device reported enroll progress, reported 7 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.228: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.228: Processing command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.228: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.228: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.228: Device reported enroll progress, reported 8 of 8 have been completed 277s (process:1999): libfprint-device-DEBUG: 17:02:35.228: Device reported enroll completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.228: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.229: Print for finger FP_FINGER_UNKNOWN enrolled 277s (process:1999): libfprint-device-DEBUG: 17:02:35.229: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.229: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.229: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.229: Got instructions of length 5 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.229: Received command CONT 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.229: Processing command CONT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.229: Device reported deletion completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.229: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.229: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.229: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.229: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.229: Received command SET_KEEP_ALIVE 0 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.229: Keep alive toggled: 0 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.230: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.230: Got instructions of length 19 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.230: Received command SET_ENROLL_STAGES 5 277s (process:1999): libfprint-device-DEBUG: 17:02:35.230: Device reported close completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.230: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.230: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s ok 277s test_enroll_script_interactive (__main__.VirtualDeviceStorage.test_enroll_script_interactive) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.230: 111215418: ../libfprint/drivers/virtual-device.c:387 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.230: 111215461: ../libfprint/drivers/virtual-device-listener.c:153 277s (process:1999): libfprint-device-DEBUG: 17:02:35.230: Device reported open completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.230: Completing action FPI_DEVICE_ACTION_OPEN in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.230: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.230: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.230: Got instructions of length 8 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.231: Received command SLEEP 50 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.231: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.231: Got instructions of length 13 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.231: Received command SCAN print-id 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.231: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.231: Got instructions of length 13 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.231: Received command SCAN print-id 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.231: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.231: Got instructions of length 7 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.231: Received command RETRY 1 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.231: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.231: Got instructions of length 13 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.231: Received command SCAN print-id 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.232: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.232: Got instructions of length 8 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.232: Received command SLEEP 50 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.232: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.232: Got instructions of length 13 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.232: Received command SCAN print-id 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.232: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.232: Got instructions of length 7 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.232: Received command RETRY 2 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.232: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.232: Got instructions of length 15 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.232: Received command SCAN another-id 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.232: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.232: Got instructions of length 13 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.232: Received command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.233: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.233: Processing command SLEEP 50 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.233: Sleeping 50ms 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.283: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.283: Processing command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.283: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.283: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.283: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.283: Device reported enroll progress, reported 1 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.283: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.283: Processing command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.283: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.283: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.283: Device reported enroll progress, reported 2 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.283: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.283: Processing command RETRY 1 277s (process:1999): libfprint-device-DEBUG: 17:02:35.283: Device reported enroll progress, reported 2 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.283: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.283: Processing command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.283: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.283: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.283: Device reported enroll progress, reported 3 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.283: Processing command SLEEP 50 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.283: Sleeping 50ms 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.333: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.333: Processing command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.333: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.333: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.333: Device reported enroll progress, reported 4 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.333: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.333: Processing command RETRY 2 277s (process:1999): libfprint-device-DEBUG: 17:02:35.333: Device reported enroll progress, reported 4 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.333: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.333: Processing command SCAN another-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.333: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.333: Device reported enroll progress, reported 4 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.333: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.333: Processing command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.333: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.333: Device reported enroll progress, reported 5 of 5 have been completed 277s (process:1999): libfprint-device-DEBUG: 17:02:35.333: Device reported enroll completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.333: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.333: Print for finger FP_FINGER_UNKNOWN enrolled 277s (process:1999): libfprint-device-DEBUG: 17:02:35.333: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.333: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.333: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.333: Got instructions of length 5 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.334: Received command CONT 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.334: Processing command CONT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.334: Device reported deletion completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.334: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.334: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.334: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.334: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.334: Received command SET_KEEP_ALIVE 0 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.334: Keep alive toggled: 0 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.334: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.334: Got instructions of length 19 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.334: Received command SET_ENROLL_STAGES 5 277s (process:1999): libfprint-device-DEBUG: 17:02:35.334: Device reported close completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.334: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.334: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s ok 277s test_enroll_verify_error (__main__.VirtualDeviceStorage.test_enroll_verify_error) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.334: 111319259: ../libfprint/drivers/virtual-device.c:387 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.334: 111319267: ../libfprint/drivers/virtual-device-listener.c:153 277s (process:1999): libfprint-device-DEBUG: 17:02:35.334: Device reported open completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.334: Completing action FPI_DEVICE_ACTION_OPEN in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.334: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.334: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.334: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.334: Received command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.334: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.334: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.334: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.334: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.334: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.334: Device reported enroll progress, reported 1 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.334: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.334: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.334: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.334: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.334: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.334: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.334: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.334: Device reported enroll progress, reported 2 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.334: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.334: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.334: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.334: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.334: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.334: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.334: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.334: Device reported enroll progress, reported 3 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.334: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.335: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.335: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.335: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.335: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.335: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.335: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.335: Device reported enroll progress, reported 4 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.335: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.335: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.335: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.335: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.335: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.335: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.335: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.335: Device reported enroll progress, reported 5 of 5 have been completed 277s (process:1999): libfprint-device-DEBUG: 17:02:35.335: Device reported enroll completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.335: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.335: Print for finger FP_FINGER_LEFT_RING enrolled 277s (process:1999): libfprint-device-DEBUG: 17:02:35.335: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.335: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.336: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.336: Got instructions of length 7 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.336: Received command ERROR 0 277s (process:1999): libfprint-device-DEBUG: 17:02:35.336: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.336: Processing command ERROR 0 277s (process:1999): libfprint-device-DEBUG: 17:02:35.336: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.336: Device reported identify completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.336: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.336: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.336: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.336: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.336: Got instructions of length 5 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.336: Received command CONT 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.336: Processing command CONT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.337: Device reported deletion completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.337: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.337: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.337: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.337: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.337: Received command SET_KEEP_ALIVE 0 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.337: Keep alive toggled: 0 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.337: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.337: Got instructions of length 19 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.337: Received command SET_ENROLL_STAGES 5 277s (process:1999): libfprint-device-DEBUG: 17:02:35.337: Device reported close completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.337: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.337: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s Enroll done 277s ok 277s test_enroll_verify_match (__main__.VirtualDeviceStorage.test_enroll_verify_match) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.337: 111322265: ../libfprint/drivers/virtual-device.c:387 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.337: 111322272: ../libfprint/drivers/virtual-device-listener.c:153 277s (process:1999): libfprint-device-DEBUG: 17:02:35.337: Device reported open completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.337: Completing action FPI_DEVICE_ACTION_OPEN in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.337: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.337: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.337: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.337: Received command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.337: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.337: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.337: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.337: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.337: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.337: Device reported enroll progress, reported 1 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.337: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.337: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.337: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.337: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.337: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.337: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.337: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.337: Device reported enroll progress, reported 2 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.337: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.337: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.337: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.337: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.337: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.337: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.337: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.337: Device reported enroll progress, reported 3 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.337: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.337: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.338: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.338: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.338: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Device reported enroll progress, reported 4 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.338: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.338: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.338: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.338: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.338: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Device reported enroll progress, reported 5 of 5 have been completed 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Device reported enroll completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Print for finger FP_FINGER_LEFT_THUMB enrolled 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.338: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.338: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.338: Received command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.338: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-virtual_device_storage-DEBUG: 17:02:35.338: Trying to identify print 'testprint' against a gallery of 1 prints 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Device reported identify result 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Device reported identify completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.338: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.338: Got instructions of length 5 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.338: Received command CONT 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.338: Processing command CONT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Device reported deletion completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.338: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.338: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.338: Received command SET_KEEP_ALIVE 0 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.338: Keep alive toggled: 0 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.338: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.338: Got instructions of length 19 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.338: Received command SET_ENROLL_STAGES 5 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Device reported close completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s Enroll done 277s ok 277s test_enroll_verify_no_match (__main__.VirtualDeviceStorage.test_enroll_verify_no_match) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.338: 111323770: ../libfprint/drivers/virtual-device.c:387 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.338: 111323776: ../libfprint/drivers/virtual-device-listener.c:153 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Device reported open completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Completing action FPI_DEVICE_ACTION_OPEN in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.338: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.339: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.339: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.339: Received command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.339: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.339: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.339: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.339: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.339: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.339: Device reported enroll progress, reported 1 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.339: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.339: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.339: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.339: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.339: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.339: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.339: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.339: Device reported enroll progress, reported 2 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.339: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.340: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.340: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.340: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.340: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.340: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.340: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.340: Device reported enroll progress, reported 3 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.340: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.340: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.340: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.340: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.340: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.340: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.340: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.340: Device reported enroll progress, reported 4 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.340: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.340: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.340: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.341: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.341: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.341: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.341: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.341: Device reported enroll progress, reported 5 of 5 have been completed 277s (process:1999): libfprint-device-DEBUG: 17:02:35.341: Device reported enroll completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.341: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.341: Print for finger FP_FINGER_LEFT_RING enrolled 277s (process:1999): libfprint-device-DEBUG: 17:02:35.341: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.341: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.341: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.341: Got instructions of length 18 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.341: Received command SCAN not-testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.341: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.341: Processing command SCAN not-testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.341: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.341: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-virtual_device_storage-DEBUG: 17:02:35.341: Trying to identify print 'not-testprint' against a gallery of 1 prints 277s (process:1999): libfprint-device-DEBUG: 17:02:35.341: Device reported identify result 277s (process:1999): libfprint-device-DEBUG: 17:02:35.342: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.342: Device reported identify completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.342: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.342: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.342: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.342: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.342: Got instructions of length 5 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.342: Received command CONT 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.342: Processing command CONT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.342: Device reported deletion completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.342: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.342: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.342: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.342: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.342: Received command SET_KEEP_ALIVE 0 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.342: Keep alive toggled: 0 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.342: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.343: Got instructions of length 19 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.343: Received command SET_ENROLL_STAGES 5 277s (process:1999): libfprint-device-DEBUG: 17:02:35.343: Device reported close completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.343: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.343: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s Enroll done 277s ok 277s test_enroll_verify_retry (__main__.VirtualDeviceStorage.test_enroll_verify_retry) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.343: 111328325: ../libfprint/drivers/virtual-device.c:387 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.343: 111328335: ../libfprint/drivers/virtual-device-listener.c:153 277s (process:1999): libfprint-device-DEBUG: 17:02:35.343: Device reported open completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.343: Completing action FPI_DEVICE_ACTION_OPEN in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.343: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.343: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.343: Got instructions of length 7 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.343: Received command RETRY 1 277s (process:1999): libfprint-device-DEBUG: 17:02:35.343: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.343: Processing command RETRY 1 277s (process:1999): libfprint-device-DEBUG: 17:02:35.343: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.343: Virtual device scan failed with error: The swipe was too short, please try again. 277s (process:1999): libfprint-device-DEBUG: 17:02:35.343: Device reported verify result 277s (process:1999): libfprint-device-DEBUG: 17:02:35.343: Device reported verify completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.343: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.343: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.343: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.343: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.343: Got instructions of length 5 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.343: Received command CONT 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.343: Processing command CONT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.343: Device reported deletion completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.343: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.343: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.343: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.343: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.343: Received command SET_KEEP_ALIVE 0 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.343: Keep alive toggled: 0 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.344: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.344: Got instructions of length 19 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.344: Received command SET_ENROLL_STAGES 5 277s (process:1999): libfprint-device-DEBUG: 17:02:35.344: Device reported close completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.344: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.344: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s ok 277s test_enroll_verify_script (__main__.VirtualDeviceStorage.test_enroll_verify_script) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.344: 111329070: ../libfprint/drivers/virtual-device.c:387 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.344: 111329076: ../libfprint/drivers/virtual-device-listener.c:153 277s (process:1999): libfprint-device-DEBUG: 17:02:35.344: Device reported open completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.344: Completing action FPI_DEVICE_ACTION_OPEN in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.344: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.344: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.344: Got instructions of length 19 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.344: Received command SET_ENROLL_STAGES 8 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.344: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.344: Got instructions of length 13 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.344: Received command SCAN print-id 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.344: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.344: Got instructions of length 13 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.344: Received command SCAN print-id 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.344: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.344: Got instructions of length 7 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.344: Received command RETRY 1 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.344: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.344: Got instructions of length 13 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.344: Received command SCAN print-id 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.344: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.344: Got instructions of length 7 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.344: Received command RETRY 3 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.344: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.344: Got instructions of length 13 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.344: Received command SCAN print-id 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.344: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.344: Got instructions of length 7 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.344: Received command RETRY 2 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.344: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.344: Got instructions of length 13 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.344: Received command SCAN print-id 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.344: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.344: Got instructions of length 8 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.344: Received command SLEEP 10 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.345: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Got instructions of length 8 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Received command SLEEP 20 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.345: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Got instructions of length 7 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Received command RETRY 0 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.345: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Got instructions of length 7 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Received command RETRY 3 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.345: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Got instructions of length 13 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Received command SCAN print-id 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.345: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Got instructions of length 15 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Received command SCAN another-id 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.345: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Got instructions of length 13 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Received command SCAN print-id 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.345: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Got instructions of length 13 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Received command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.345: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Processing command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.345: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.345: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.345: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.345: Device reported enroll progress, reported 1 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Processing command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.345: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.345: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.345: Device reported enroll progress, reported 2 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Processing command RETRY 1 277s (process:1999): libfprint-device-DEBUG: 17:02:35.345: Device reported enroll progress, reported 2 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Processing command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.345: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.345: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.345: Device reported enroll progress, reported 3 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Processing command RETRY 3 277s (process:1999): libfprint-device-DEBUG: 17:02:35.345: Device reported enroll progress, reported 3 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Processing command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.345: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.345: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.345: Device reported enroll progress, reported 4 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Processing command RETRY 2 277s (process:1999): libfprint-device-DEBUG: 17:02:35.345: Device reported enroll progress, reported 4 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Processing command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.345: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.345: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.345: Device reported enroll progress, reported 5 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Processing command SLEEP 10 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.345: Sleeping 10ms 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.355: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.355: Processing command SLEEP 20 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.355: Sleeping 20ms 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.375: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.375: Processing command RETRY 0 277s (process:1999): libfprint-device-DEBUG: 17:02:35.375: Device reported enroll progress, reported 5 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.375: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.375: Processing command RETRY 3 277s (process:1999): libfprint-device-DEBUG: 17:02:35.375: Device reported enroll progress, reported 5 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.375: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.375: Processing command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.375: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.375: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.375: Device reported enroll progress, reported 6 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.375: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.375: Processing command SCAN another-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.375: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.375: Device reported enroll progress, reported 6 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.375: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.375: Processing command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.375: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.375: Device reported enroll progress, reported 7 of 8 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.375: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.375: Processing command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.375: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.375: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.375: Device reported enroll progress, reported 8 of 8 have been completed 277s (process:1999): libfprint-device-DEBUG: 17:02:35.375: Device reported enroll completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.375: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.375: Print for finger FP_FINGER_UNKNOWN enrolled 277s (process:1999): libfprint-device-DEBUG: 17:02:35.376: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.376: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.376: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.376: Got instructions of length 7 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.376: Received command RETRY 2 277s (process:1999): libfprint-device-DEBUG: 17:02:35.376: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.376: Processing command RETRY 2 277s (process:1999): libfprint-device-DEBUG: 17:02:35.376: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.376: Virtual device scan failed with error: The finger was not centered properly, please try again. 277s (process:1999): libfprint-device-DEBUG: 17:02:35.376: Device reported verify result 277s (process:1999): libfprint-device-DEBUG: 17:02:35.376: Device reported verify completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.376: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.376: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.376: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.376: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.376: Got instructions of length 8 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.376: Received command SLEEP 50 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.376: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.376: Got instructions of length 7 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.376: Received command RETRY 1 277s (process:1999): libfprint-device-DEBUG: 17:02:35.376: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.376: Processing command SLEEP 50 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.376: Sleeping 50ms 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.426: Sleeping completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.426: Processing command RETRY 1 277s (process:1999): libfprint-device-DEBUG: 17:02:35.426: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.426: Virtual device scan failed with error: The swipe was too short, please try again. 277s (process:1999): libfprint-device-DEBUG: 17:02:35.426: Device reported verify result 277s (process:1999): libfprint-device-DEBUG: 17:02:35.426: Device reported verify completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.426: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.426: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.426: Updated temperature model after 0.05 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.426: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.427: Got instructions of length 15 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.427: Received command SCAN another-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.427: Processing command SCAN another-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.427: Virtual device scanned print another-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Device reported verify result 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Device reported verify completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.427: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.427: Got instructions of length 13 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.427: Received command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.427: Processing command SCAN print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.427: Virtual device scanned print print-id 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Device reported verify result 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Device reported verify completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.427: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.427: Got instructions of length 5 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.427: Received command CONT 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.427: Processing command CONT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Device reported deletion completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.427: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.427: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.427: Received command SET_KEEP_ALIVE 0 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.427: Keep alive toggled: 0 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.427: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.427: Got instructions of length 19 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.427: Received command SET_ENROLL_STAGES 5 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Device reported close completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s ok 277s test_enroll_with_retry (__main__.VirtualDeviceStorage.test_enroll_with_retry) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.427: 111412758: ../libfprint/drivers/virtual-device.c:387 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.427: 111412765: ../libfprint/drivers/virtual-device-listener.c:153 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Device reported open completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Completing action FPI_DEVICE_ACTION_OPEN in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.427: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.428: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.428: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.428: Received command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.428: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.428: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.428: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.428: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.428: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.428: Device reported enroll progress, reported 1 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.428: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.428: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.428: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.428: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.428: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.428: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.428: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.428: Device reported enroll progress, reported 2 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.428: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.428: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.428: Got instructions of length 7 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.428: Received command RETRY 1 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.428: Processing command RETRY 1 277s (process:1999): libfprint-device-DEBUG: 17:02:35.428: Device reported enroll progress, reported 2 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.428: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.428: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.428: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.428: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.428: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.428: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.428: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.428: Device reported enroll progress, reported 3 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.428: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.428: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.428: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.428: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.428: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.428: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.428: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.428: Device reported enroll progress, reported 4 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.428: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.428: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.428: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.428: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.428: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.428: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.428: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.428: Device reported enroll progress, reported 5 of 5 have been completed 277s (process:1999): libfprint-device-DEBUG: 17:02:35.428: Device reported enroll completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.428: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.428: Print for finger FP_FINGER_LEFT_LITTLE enrolled 277s (process:1999): libfprint-device-DEBUG: 17:02:35.428: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.428: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.429: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.429: Got instructions of length 5 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.429: Received command CONT 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.429: Processing command CONT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.429: Device reported deletion completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.429: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.429: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.429: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.429: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.429: Received command SET_KEEP_ALIVE 0 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.429: Keep alive toggled: 0 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.429: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.429: Got instructions of length 19 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.429: Received command SET_ENROLL_STAGES 5 277s (process:1999): libfprint-device-DEBUG: 17:02:35.429: Device reported close completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.429: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.429: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s Enroll done 277s ok 277s test_finger_status (__main__.VirtualDeviceStorage.test_finger_status) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.429: 111414264: ../libfprint/drivers/virtual-device.c:387 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.429: 111414270: ../libfprint/drivers/virtual-device-listener.c:153 277s (process:1999): libfprint-device-DEBUG: 17:02:35.429: Device reported open completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.429: Completing action FPI_DEVICE_ACTION_OPEN in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.429: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-device-DEBUG: 17:02:35.429: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-device-DEBUG: 17:02:35.429: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.429: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.429: Got instructions of length 8 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.429: Received command FINGER 1 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.429: Processing command FINGER 1 277s (process:1999): libfprint-device-DEBUG: 17:02:35.429: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.429: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.429: Got instructions of length 8 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.429: Received command FINGER 0 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.429: Processing command FINGER 0 277s (process:1999): libfprint-device-DEBUG: 17:02:35.429: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.429: Idle cancelling on ongoing operation! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.429: Got cancellation! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.429: Device reported identify completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.429: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.429: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.429: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.429: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.429: Got instructions of length 5 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.429: Received command CONT 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.429: Processing command CONT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.429: Device reported deletion completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.429: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.429: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.430: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.430: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.430: Received command SET_KEEP_ALIVE 0 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.430: Keep alive toggled: 0 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.430: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.430: Got instructions of length 19 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.430: Received command SET_ENROLL_STAGES 5 277s (process:1999): libfprint-device-DEBUG: 17:02:35.430: Device reported close completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.430: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.430: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s ok 277s test_finger_status_after_sleep (__main__.VirtualDeviceStorage.test_finger_status_after_sleep) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.430: 111415115: ../libfprint/drivers/virtual-device.c:387 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.430: 111415121: ../libfprint/drivers/virtual-device-listener.c:153 277s (process:1999): libfprint-device-DEBUG: 17:02:35.430: Device reported open completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.430: Completing action FPI_DEVICE_ACTION_OPEN in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.430: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.430: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.430: Got instructions of length 8 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.430: Received command SLEEP 10 277s (process:1999): libfprint-device-DEBUG: 17:02:35.430: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.430: Processing command SLEEP 10 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.430: Sleeping 10ms 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.440: Sleeping completed 277s (process:1999): libfprint-device-DEBUG: 17:02:35.440: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.440: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.440: Got instructions of length 8 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.440: Received command FINGER 1 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.440: Processing command FINGER 1 277s (process:1999): libfprint-device-DEBUG: 17:02:35.440: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.440: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.440: Got instructions of length 8 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.440: Received command FINGER 0 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.440: Processing command FINGER 0 277s (process:1999): libfprint-device-DEBUG: 17:02:35.440: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.440: Idle cancelling on ongoing operation! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.440: Got cancellation! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.440: Device reported identify completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.440: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.440: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.440: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.441: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.441: Got instructions of length 5 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.441: Received command CONT 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.441: Processing command CONT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.441: Device reported deletion completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.441: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.441: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.441: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.441: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.441: Received command SET_KEEP_ALIVE 0 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.441: Keep alive toggled: 0 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.441: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.441: Got instructions of length 19 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.441: Received command SET_ENROLL_STAGES 5 277s (process:1999): libfprint-device-DEBUG: 17:02:35.441: Device reported close completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.441: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.441: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s ok 277s test_identify_match (__main__.VirtualDeviceStorage.test_identify_match) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.441: 111426318: ../libfprint/drivers/virtual-device.c:387 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.441: 111426324: ../libfprint/drivers/virtual-device-listener.c:153 277s (process:1999): libfprint-device-DEBUG: 17:02:35.441: Device reported open completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.441: Completing action FPI_DEVICE_ACTION_OPEN in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.441: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.441: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.441: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.441: Received command SCAN right-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.441: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.441: Processing command SCAN right-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.441: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.441: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.441: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.441: Device reported enroll progress, reported 1 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.441: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.441: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.441: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.441: Received command SCAN right-thumb 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.441: Processing command SCAN right-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.441: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.441: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.441: Device reported enroll progress, reported 2 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.441: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.441: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.441: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.441: Received command SCAN right-thumb 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.441: Processing command SCAN right-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.441: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.441: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.441: Device reported enroll progress, reported 3 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.441: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.442: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.442: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.442: Received command SCAN right-thumb 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.442: Processing command SCAN right-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.442: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.442: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.442: Device reported enroll progress, reported 4 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.442: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.442: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.442: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.442: Received command SCAN right-thumb 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.442: Processing command SCAN right-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.442: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.442: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.442: Device reported enroll progress, reported 5 of 5 have been completed 277s (process:1999): libfprint-device-DEBUG: 17:02:35.442: Device reported enroll completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.442: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.442: Print for finger FP_FINGER_RIGHT_THUMB enrolled 277s (process:1999): libfprint-device-DEBUG: 17:02:35.442: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.442: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.442: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.442: Got instructions of length 15 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.442: Received command SCAN left-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.442: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.442: Processing command SCAN left-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.442: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.442: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.442: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.442: Device reported enroll progress, reported 1 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.442: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.442: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.442: Got instructions of length 15 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.442: Received command SCAN left-thumb 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.442: Processing command SCAN left-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.442: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.442: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.442: Device reported enroll progress, reported 2 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.442: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.442: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.442: Got instructions of length 15 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.442: Received command SCAN left-thumb 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.442: Processing command SCAN left-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.442: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.442: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.442: Device reported enroll progress, reported 3 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.442: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.442: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.442: Got instructions of length 15 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.442: Received command SCAN left-thumb 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.442: Processing command SCAN left-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.442: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.442: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.442: Device reported enroll progress, reported 4 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.442: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.443: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.443: Got instructions of length 15 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.443: Received command SCAN left-thumb 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.443: Processing command SCAN left-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.443: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.443: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.443: Device reported enroll progress, reported 5 of 5 have been completed 277s (process:1999): libfprint-device-DEBUG: 17:02:35.443: Device reported enroll completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.443: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.443: Print for finger FP_FINGER_LEFT_THUMB enrolled 277s (process:1999): libfprint-device-DEBUG: 17:02:35.443: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.443: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.443: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.443: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.443: Received command SCAN right-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.443: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.443: Processing command SCAN right-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.443: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.443: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-virtual_device_storage-DEBUG: 17:02:35.443: Trying to identify print 'right-thumb' against a gallery of 2 prints 277s (process:1999): libfprint-device-DEBUG: 17:02:35.443: Device reported identify result 277s (process:1999): libfprint-device-DEBUG: 17:02:35.443: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.443: Device reported identify completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.443: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.444: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.444: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.444: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.444: Got instructions of length 15 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.444: Received command SCAN left-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.444: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.444: Processing command SCAN left-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.444: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.444: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-virtual_device_storage-DEBUG: 17:02:35.444: Trying to identify print 'left-thumb' against a gallery of 2 prints 277s (process:1999): libfprint-device-DEBUG: 17:02:35.444: Device reported identify result 277s (process:1999): libfprint-device-DEBUG: 17:02:35.444: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.444: Device reported identify completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.444: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.444: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.444: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.444: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.445: Got instructions of length 5 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.445: Received command CONT 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.445: Processing command CONT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.445: Device reported deletion completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.445: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.445: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.445: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.445: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.445: Received command SET_KEEP_ALIVE 0 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.445: Keep alive toggled: 0 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.445: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.445: Got instructions of length 19 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.445: Received command SET_ENROLL_STAGES 5 277s (process:1999): libfprint-device-DEBUG: 17:02:35.445: Device reported close completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.445: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.445: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s Enroll done 277s Enroll done 277s ok 277s test_identify_missing_print (__main__.VirtualDeviceStorage.test_identify_missing_print) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.446: 111430951: ../libfprint/drivers/virtual-device.c:387 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.446: 111430994: ../libfprint/drivers/virtual-device-listener.c:153 277s (process:1999): libfprint-device-DEBUG: 17:02:35.446: Device reported open completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.446: Completing action FPI_DEVICE_ACTION_OPEN in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.446: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.446: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.446: Got instructions of length 23 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.446: Received command SCAN not-existing-print 277s (process:1999): libfprint-device-DEBUG: 17:02:35.446: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.446: Processing command SCAN not-existing-print 277s (process:1999): libfprint-device-DEBUG: 17:02:35.446: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.446: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-virtual_device_storage-DEBUG: 17:02:35.446: Trying to identify print 'not-existing-print' against a gallery of 1 prints 277s (process:1999): libfprint-device-DEBUG: 17:02:35.446: Device reported identify result 277s (process:1999): libfprint-device-DEBUG: 17:02:35.446: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.446: Device reported identify completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.446: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.446: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.446: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.446: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.446: Got instructions of length 5 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.446: Received command CONT 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.446: Processing command CONT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.446: Device reported deletion completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.446: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.446: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.446: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.446: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.446: Received command SET_KEEP_ALIVE 0 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.446: Keep alive toggled: 0 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.446: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.446: Got instructions of length 19 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.446: Received command SET_ENROLL_STAGES 5 277s (process:1999): libfprint-device-DEBUG: 17:02:35.446: Device reported close completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.446: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.446: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s ok 277s test_identify_no_match (__main__.VirtualDeviceStorage.test_identify_no_match) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.446: 111431895: ../libfprint/drivers/virtual-device.c:387 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.446: 111431902: ../libfprint/drivers/virtual-device-listener.c:153 277s (process:1999): libfprint-device-DEBUG: 17:02:35.447: Device reported open completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.447: Completing action FPI_DEVICE_ACTION_OPEN in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.447: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.447: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.447: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.447: Received command SCAN right-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.447: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.447: Processing command SCAN right-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.447: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.447: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.447: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.447: Device reported enroll progress, reported 1 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.447: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.447: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.447: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.447: Received command SCAN right-thumb 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.447: Processing command SCAN right-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.447: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.448: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.448: Device reported enroll progress, reported 2 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.448: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.448: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.448: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.448: Received command SCAN right-thumb 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.448: Processing command SCAN right-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.448: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.448: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.448: Device reported enroll progress, reported 3 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.448: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.448: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.448: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.448: Received command SCAN right-thumb 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.448: Processing command SCAN right-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.448: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.448: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.448: Device reported enroll progress, reported 4 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.449: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.449: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.449: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.449: Received command SCAN right-thumb 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.449: Processing command SCAN right-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.449: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.449: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.449: Device reported enroll progress, reported 5 of 5 have been completed 277s (process:1999): libfprint-device-DEBUG: 17:02:35.449: Device reported enroll completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.449: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.449: Print for finger FP_FINGER_RIGHT_THUMB enrolled 277s (process:1999): libfprint-device-DEBUG: 17:02:35.449: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.449: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.449: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.449: Got instructions of length 15 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.450: Received command SCAN left-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.450: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.450: Processing command SCAN left-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.450: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.450: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.450: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.450: Device reported enroll progress, reported 1 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.450: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.450: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.450: Got instructions of length 15 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.450: Received command SCAN left-thumb 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.450: Processing command SCAN left-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.450: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.450: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.450: Device reported enroll progress, reported 2 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.450: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.450: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.450: Got instructions of length 15 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.450: Received command SCAN left-thumb 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.450: Processing command SCAN left-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.450: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.450: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.450: Device reported enroll progress, reported 3 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.450: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.450: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.450: Got instructions of length 15 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.450: Received command SCAN left-thumb 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.450: Processing command SCAN left-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.450: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.450: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.450: Device reported enroll progress, reported 4 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.450: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.451: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.451: Got instructions of length 15 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.451: Received command SCAN left-thumb 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.451: Processing command SCAN left-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.451: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.451: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.451: Device reported enroll progress, reported 5 of 5 have been completed 277s (process:1999): libfprint-device-DEBUG: 17:02:35.451: Device reported enroll completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.451: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.451: Print for finger FP_FINGER_LEFT_THUMB enrolled 277s (process:1999): libfprint-device-DEBUG: 17:02:35.451: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.451: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.451: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.451: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.451: Received command SCAN right-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.451: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.451: Processing command SCAN right-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.451: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.451: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-virtual_device_storage-DEBUG: 17:02:35.451: Trying to identify print 'right-thumb' against a gallery of 1 prints 277s (process:1999): libfprint-device-DEBUG: 17:02:35.451: Device reported identify result 277s (process:1999): libfprint-device-DEBUG: 17:02:35.451: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.451: Device reported identify completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.451: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.451: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.451: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.451: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.451: Got instructions of length 15 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.451: Received command SCAN left-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.451: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.451: Processing command SCAN left-thumb 277s (process:1999): libfprint-device-DEBUG: 17:02:35.451: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.451: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-virtual_device_storage-DEBUG: 17:02:35.451: Trying to identify print 'left-thumb' against a gallery of 1 prints 277s (process:1999): libfprint-device-DEBUG: 17:02:35.451: Device reported identify result 277s (process:1999): libfprint-device-DEBUG: 17:02:35.451: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.451: Device reported identify completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.451: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.452: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.452: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.452: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.452: Got instructions of length 5 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.452: Received command CONT 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.452: Processing command CONT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.452: Device reported deletion completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.452: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.452: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.452: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.452: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.452: Received command SET_KEEP_ALIVE 0 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.452: Keep alive toggled: 0 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.452: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.452: Got instructions of length 19 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.452: Received command SET_ENROLL_STAGES 5 277s (process:1999): libfprint-device-DEBUG: 17:02:35.452: Device reported close completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.452: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.452: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s Enroll done 277s Enroll done 277s ok 277s test_identify_retry (__main__.VirtualDeviceStorage.test_identify_retry) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.452: 111437336: ../libfprint/drivers/virtual-device.c:387 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.452: 111437343: ../libfprint/drivers/virtual-device-listener.c:153 277s (process:1999): libfprint-device-DEBUG: 17:02:35.452: Device reported open completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.452: Completing action FPI_DEVICE_ACTION_OPEN in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.452: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.452: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.452: Got instructions of length 7 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.452: Received command RETRY 1 277s (process:1999): libfprint-device-DEBUG: 17:02:35.452: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.452: Processing command RETRY 1 277s (process:1999): libfprint-device-DEBUG: 17:02:35.452: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.452: Device reported identify result 277s (process:1999): libfprint-device-DEBUG: 17:02:35.452: Device reported identify completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.452: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.452: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.452: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.452: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.452: Got instructions of length 5 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.452: Received command CONT 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.452: Processing command CONT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.452: Device reported deletion completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.452: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.452: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.452: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.452: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.452: Received command SET_KEEP_ALIVE 0 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.452: Keep alive toggled: 0 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.453: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.453: Got instructions of length 19 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.453: Received command SET_ENROLL_STAGES 5 277s (process:1999): libfprint-device-DEBUG: 17:02:35.453: Device reported close completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.453: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.453: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s ok 277s test_identify_unsupported (__main__.VirtualDeviceStorage.test_identify_unsupported) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.453: 111438074: ../libfprint/drivers/virtual-device.c:387 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.453: 111438080: ../libfprint/drivers/virtual-device-listener.c:153 277s (process:1999): libfprint-device-DEBUG: 17:02:35.453: Device reported open completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.453: Completing action FPI_DEVICE_ACTION_OPEN in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.453: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s skipped 'Device supports identification' 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.453: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.453: Got instructions of length 5 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.453: Received command CONT 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.453: Processing command CONT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.453: Device reported deletion completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.453: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.453: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.453: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.453: Got instructions of length 16 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.453: Received command SET_KEEP_ALIVE 0 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.453: Keep alive toggled: 0 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.453: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.453: Got instructions of length 19 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.453: Received command SET_ENROLL_STAGES 5 277s (process:1999): libfprint-device-DEBUG: 17:02:35.453: Device reported close completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.453: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.453: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s test_list_delete (__main__.VirtualDeviceStorage.test_list_delete) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.453: 111438565: ../libfprint/drivers/virtual-device.c:387 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.453: 111438571: ../libfprint/drivers/virtual-device-listener.c:153 277s (process:1999): libfprint-device-DEBUG: 17:02:35.453: Device reported open completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.453: Completing action FPI_DEVICE_ACTION_OPEN in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.453: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.453: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.453: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.453: Received command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.453: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.453: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.453: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.453: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.453: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.453: Device reported enroll progress, reported 1 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.453: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.454: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.454: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.454: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.454: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.454: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.454: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.454: Device reported enroll progress, reported 2 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.454: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.454: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.454: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.454: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.454: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.454: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.454: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.454: Device reported enroll progress, reported 3 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.454: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.454: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.454: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.454: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.454: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.454: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.454: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.454: Device reported enroll progress, reported 4 of 5 have been completed 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.454: Sleeping completed 277s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:35.454: Got a new connection! 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.454: Got instructions of length 14 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.454: Received command SCAN testprint 277s (process:1999): libfprint-virtual_device-DEBUG: 17:02:35.454: Processing command SCAN testprint 277s (process:1999): libfprint-device-DEBUG: 17:02:35.454: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 277s (process:1999): libfprint-device-DEBUG: 17:02:35.454: Device reported finger status change: FP_FINGER_STATUS_NEEDED 277s (process:1999): libfprint-device-DEBUG: 17:02:35.454: Device reported enroll progress, reported 5 of 5 have been completed 277s (process:1999): libfprint-device-DEBUG: 17:02:35.454: Device reported enroll completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.454: Device reported finger status change: FP_FINGER_STATUS_NONE 277s (process:1999): libfprint-device-DEBUG: 17:02:35.454: Print for finger FP_FINGER_RIGHT_THUMB enrolled 277s (process:1999): libfprint-device-DEBUG: 17:02:35.454: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.454: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s (process:1999): libfprint-device-DEBUG: 17:02:35.955: Device reported listing completion 277s (process:1999): libfprint-device-DEBUG: 17:02:35.955: Completing action FPI_DEVICE_ACTION_LIST in idle! 277s (process:1999): libfprint-device-DEBUG: 17:02:35.955: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s Executing: libfprint-2/virtual-device.test 278s (process:1999): libfprint-virtual_device_storage-DEBUG: 17:02:36.455: Deleting print testprint for user testuser 278s (process:1999): libfprint-device-DEBUG: 17:02:36.456: Device reported deletion completion 278s (process:1999): libfprint-device-DEBUG: 17:02:36.456: Completing action FPI_DEVICE_ACTION_DELETE in idle! 278s (process:1999): libfprint-device-DEBUG: 17:02:36.456: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s (process:1999): libfprint-device-DEBUG: 17:02:36.956: Device reported listing completion 278s (process:1999): libfprint-device-DEBUG: 17:02:36.956: Completing action FPI_DEVICE_ACTION_LIST in idle! 278s (process:1999): libfprint-device-DEBUG: 17:02:36.956: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:36.956: Got a new connection! 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.956: Got instructions of length 5 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.956: Received command CONT 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.957: Processing command CONT 278s (process:1999): libfprint-device-DEBUG: 17:02:36.957: Device reported deletion completion 278s (process:1999): libfprint-device-DEBUG: 17:02:36.957: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 278s (process:1999): libfprint-device-DEBUG: 17:02:36.957: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:36.957: Got a new connection! 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.957: Got instructions of length 16 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.957: Received command SET_KEEP_ALIVE 0 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.957: Keep alive toggled: 0 278s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:36.957: Got a new connection! 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.957: Got instructions of length 19 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.957: Received command SET_ENROLL_STAGES 5 278s (process:1999): libfprint-device-DEBUG: 17:02:36.957: Device reported close completion 278s (process:1999): libfprint-device-DEBUG: 17:02:36.957: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 278s (process:1999): libfprint-device-DEBUG: 17:02:36.957: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s Enroll done 278s 278s blub 'testprint' 278s ok 278s test_list_delete_missing (__main__.VirtualDeviceStorage.test_list_delete_missing) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.957: 112942278: ../libfprint/drivers/virtual-device.c:387 278s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:36.957: 112942285: ../libfprint/drivers/virtual-device-listener.c:153 278s (process:1999): libfprint-device-DEBUG: 17:02:36.957: Device reported open completion 278s (process:1999): libfprint-device-DEBUG: 17:02:36.957: Completing action FPI_DEVICE_ACTION_OPEN in idle! 278s (process:1999): libfprint-device-DEBUG: 17:02:36.957: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:36.957: Got a new connection! 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.957: Got instructions of length 14 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.957: Received command SCAN testprint 278s (process:1999): libfprint-device-DEBUG: 17:02:36.957: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.957: Processing command SCAN testprint 278s (process:1999): libfprint-device-DEBUG: 17:02:36.957: Device reported finger status change: FP_FINGER_STATUS_NEEDED 278s (process:1999): libfprint-device-DEBUG: 17:02:36.957: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 278s (process:1999): libfprint-device-DEBUG: 17:02:36.957: Device reported finger status change: FP_FINGER_STATUS_NEEDED 278s (process:1999): libfprint-device-DEBUG: 17:02:36.957: Device reported enroll progress, reported 1 of 5 have been completed 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.957: Sleeping completed 278s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:36.957: Got a new connection! 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.957: Got instructions of length 14 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.957: Received command SCAN testprint 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.957: Processing command SCAN testprint 278s (process:1999): libfprint-device-DEBUG: 17:02:36.957: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 278s (process:1999): libfprint-device-DEBUG: 17:02:36.957: Device reported finger status change: FP_FINGER_STATUS_NEEDED 278s (process:1999): libfprint-device-DEBUG: 17:02:36.957: Device reported enroll progress, reported 2 of 5 have been completed 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.957: Sleeping completed 278s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:36.957: Got a new connection! 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.957: Got instructions of length 14 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.957: Received command SCAN testprint 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.957: Processing command SCAN testprint 278s (process:1999): libfprint-device-DEBUG: 17:02:36.957: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 278s (process:1999): libfprint-device-DEBUG: 17:02:36.957: Device reported finger status change: FP_FINGER_STATUS_NEEDED 278s (process:1999): libfprint-device-DEBUG: 17:02:36.957: Device reported enroll progress, reported 3 of 5 have been completed 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.957: Sleeping completed 278s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:36.958: Got a new connection! 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.958: Got instructions of length 14 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.958: Received command SCAN testprint 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.958: Processing command SCAN testprint 278s (process:1999): libfprint-device-DEBUG: 17:02:36.958: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 278s (process:1999): libfprint-device-DEBUG: 17:02:36.958: Device reported finger status change: FP_FINGER_STATUS_NEEDED 278s (process:1999): libfprint-device-DEBUG: 17:02:36.958: Device reported enroll progress, reported 4 of 5 have been completed 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.958: Sleeping completed 278s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:36.958: Got a new connection! 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.958: Got instructions of length 14 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.958: Received command SCAN testprint 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.958: Processing command SCAN testprint 278s (process:1999): libfprint-device-DEBUG: 17:02:36.958: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 278s (process:1999): libfprint-device-DEBUG: 17:02:36.958: Device reported finger status change: FP_FINGER_STATUS_NEEDED 278s (process:1999): libfprint-device-DEBUG: 17:02:36.958: Device reported enroll progress, reported 5 of 5 have been completed 278s (process:1999): libfprint-device-DEBUG: 17:02:36.958: Device reported enroll completion 278s (process:1999): libfprint-device-DEBUG: 17:02:36.958: Device reported finger status change: FP_FINGER_STATUS_NONE 278s (process:1999): libfprint-device-DEBUG: 17:02:36.958: Print for finger FP_FINGER_RIGHT_THUMB enrolled 278s (process:1999): libfprint-device-DEBUG: 17:02:36.958: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 278s (process:1999): libfprint-device-DEBUG: 17:02:36.958: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:36.958: Got a new connection! 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.958: Got instructions of length 16 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.958: Received command REMOVE testprint 278s (process:1999): libfprint-virtual_device-DEBUG: 17:02:36.958: Processing command REMOVE testprint 279s (process:1999): libfprint-virtual_device_storage-DEBUG: 17:02:37.459: Deleting print testprint for user testuser 279s (process:1999): libfprint-device-DEBUG: 17:02:37.459: Device reported deletion completion 279s (process:1999): libfprint-device-DEBUG: 17:02:37.459: Completing action FPI_DEVICE_ACTION_DELETE in idle! 279s (process:1999): libfprint-device-DEBUG: 17:02:37.459: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:37.459: Got a new connection! 279s (process:1999): libfprint-virtual_device-DEBUG: 17:02:37.459: Got instructions of length 5 279s (process:1999): libfprint-virtual_device-DEBUG: 17:02:37.459: Received command CONT 279s (process:1999): libfprint-virtual_device-DEBUG: 17:02:37.459: Processing command CONT 279s (process:1999): libfprint-device-DEBUG: 17:02:37.459: Device reported deletion completion 279s (process:1999): libfprint-device-DEBUG: 17:02:37.459: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 279s (process:1999): libfprint-device-DEBUG: 17:02:37.459: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:37.459: Got a new connection! 279s (process:1999): libfprint-virtual_device-DEBUG: 17:02:37.459: Got instructions of length 16 279s (process:1999): libfprint-virtual_device-DEBUG: 17:02:37.459: Received command SET_KEEP_ALIVE 0 279s (process:1999): libfprint-virtual_device-DEBUG: 17:02:37.459: Keep alive toggled: 0 279s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:37.459: Got a new connection! 279s (process:1999): libfprint-virtual_device-DEBUG: 17:02:37.459: Got instructions of length 19 279s (process:1999): libfprint-virtual_device-DEBUG: 17:02:37.459: Received command SET_ENROLL_STAGES 5 279s (process:1999): libfprint-device-DEBUG: 17:02:37.459: Device reported close completion 279s (process:1999): libfprint-device-DEBUG: 17:02:37.459: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s (process:1999): libfprint-device-DEBUG: 17:02:37.459: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s Enroll done 279s ok 279s test_list_empty (__main__.VirtualDeviceStorage.test_list_empty) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:37.459: 113444671: ../libfprint/drivers/virtual-device.c:387 279s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:37.459: 113444679: ../libfprint/drivers/virtual-device-listener.c:153 279s (process:1999): libfprint-device-DEBUG: 17:02:37.459: Device reported open completion 279s (process:1999): libfprint-device-DEBUG: 17:02:37.459: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s (process:1999): libfprint-device-DEBUG: 17:02:37.459: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s (process:1999): libfprint-device-DEBUG: 17:02:37.960: Device reported listing completion 280s (process:1999): libfprint-device-DEBUG: 17:02:37.960: Completing action FPI_DEVICE_ACTION_LIST in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:37.960: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:37.960: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:37.960: Got instructions of length 5 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:37.960: Received command CONT 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:37.960: Processing command CONT 280s (process:1999): libfprint-device-DEBUG: 17:02:37.960: Device reported deletion completion 280s (process:1999): libfprint-device-DEBUG: 17:02:37.960: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:37.960: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:37.960: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:37.960: Got instructions of length 16 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:37.960: Received command SET_KEEP_ALIVE 0 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:37.960: Keep alive toggled: 0 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:37.960: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:37.961: Got instructions of length 19 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:37.961: Received command SET_ENROLL_STAGES 5 280s (process:1999): libfprint-device-DEBUG: 17:02:37.961: Device reported close completion 280s (process:1999): libfprint-device-DEBUG: 17:02:37.961: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:37.961: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s ok 280s test_list_error (__main__.VirtualDeviceStorage.test_list_error) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:37.961: 113946081: ../libfprint/drivers/virtual-device.c:387 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:37.961: 113946089: ../libfprint/drivers/virtual-device-listener.c:153 280s (process:1999): libfprint-device-DEBUG: 17:02:37.961: Device reported open completion 280s (process:1999): libfprint-device-DEBUG: 17:02:37.961: Completing action FPI_DEVICE_ACTION_OPEN in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:37.961: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:37.961: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:37.961: Got instructions of length 9 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:37.961: Received command SLEEP 100 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:37.961: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:37.961: Got instructions of length 7 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:37.961: Received command ERROR 4 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:37.961: Processing command SLEEP 100 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:37.961: Sleeping 100ms 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.061: Sleeping completed 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.061: Processing command ERROR 4 280s (process:1999): libfprint-device-DEBUG: 17:02:38.061: Device reported listing completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.062: Completing action FPI_DEVICE_ACTION_LIST in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.062: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.062: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.062: Got instructions of length 5 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.062: Received command CONT 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.062: Processing command CONT 280s (process:1999): libfprint-device-DEBUG: 17:02:38.062: Device reported deletion completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.062: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.062: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.062: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.062: Got instructions of length 16 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.063: Received command SET_KEEP_ALIVE 0 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.063: Keep alive toggled: 0 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.063: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.063: Got instructions of length 19 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.063: Received command SET_ENROLL_STAGES 5 280s (process:1999): libfprint-device-DEBUG: 17:02:38.063: Device reported close completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.063: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.063: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s ok 280s test_list_populated (__main__.VirtualDeviceStorage.test_list_populated) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.063: 114048618: ../libfprint/drivers/virtual-device.c:387 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.063: 114048660: ../libfprint/drivers/virtual-device-listener.c:153 280s (process:1999): libfprint-device-DEBUG: 17:02:38.063: Device reported open completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.063: Completing action FPI_DEVICE_ACTION_OPEN in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.063: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.064: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.064: Got instructions of length 9 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.064: Received command INSERT p1 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.064: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.064: Got instructions of length 7 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.064: Received command SCAN p2 280s (process:1999): libfprint-device-DEBUG: 17:02:38.064: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.064: Processing command INSERT p1 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.064: Processing command SCAN p2 280s (process:1999): libfprint-device-DEBUG: 17:02:38.064: Device reported finger status change: FP_FINGER_STATUS_NEEDED 280s (process:1999): libfprint-device-DEBUG: 17:02:38.064: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 280s (process:1999): libfprint-device-DEBUG: 17:02:38.064: Device reported finger status change: FP_FINGER_STATUS_NEEDED 280s (process:1999): libfprint-device-DEBUG: 17:02:38.064: Device reported enroll progress, reported 1 of 5 have been completed 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.064: Sleeping completed 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.064: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.065: Got instructions of length 7 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.065: Received command SCAN p2 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.065: Processing command SCAN p2 280s (process:1999): libfprint-device-DEBUG: 17:02:38.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 280s (process:1999): libfprint-device-DEBUG: 17:02:38.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED 280s (process:1999): libfprint-device-DEBUG: 17:02:38.065: Device reported enroll progress, reported 2 of 5 have been completed 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.065: Sleeping completed 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.065: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.065: Got instructions of length 7 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.065: Received command SCAN p2 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.065: Processing command SCAN p2 280s (process:1999): libfprint-device-DEBUG: 17:02:38.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 280s (process:1999): libfprint-device-DEBUG: 17:02:38.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED 280s (process:1999): libfprint-device-DEBUG: 17:02:38.065: Device reported enroll progress, reported 3 of 5 have been completed 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.065: Sleeping completed 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.065: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.065: Got instructions of length 7 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.065: Received command SCAN p2 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.065: Processing command SCAN p2 280s (process:1999): libfprint-device-DEBUG: 17:02:38.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 280s (process:1999): libfprint-device-DEBUG: 17:02:38.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED 280s (process:1999): libfprint-device-DEBUG: 17:02:38.066: Device reported enroll progress, reported 4 of 5 have been completed 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.066: Sleeping completed 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.066: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.066: Got instructions of length 7 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.066: Received command SCAN p2 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.066: Processing command SCAN p2 280s (process:1999): libfprint-device-DEBUG: 17:02:38.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 280s (process:1999): libfprint-device-DEBUG: 17:02:38.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED 280s (process:1999): libfprint-device-DEBUG: 17:02:38.066: Device reported enroll progress, reported 5 of 5 have been completed 280s (process:1999): libfprint-device-DEBUG: 17:02:38.066: Device reported enroll completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.066: Device reported finger status change: FP_FINGER_STATUS_NONE 280s (process:1999): libfprint-device-DEBUG: 17:02:38.066: Print for finger FP_FINGER_LEFT_LITTLE enrolled 280s (process:1999): libfprint-device-DEBUG: 17:02:38.066: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.066: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s (process:1999): libfprint-device-DEBUG: 17:02:38.567: Device reported listing completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.567: Completing action FPI_DEVICE_ACTION_LIST in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.567: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.567: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.567: Got instructions of length 5 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.567: Received command CONT 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.567: Processing command CONT 280s (process:1999): libfprint-device-DEBUG: 17:02:38.567: Device reported deletion completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.567: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.567: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.567: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.567: Got instructions of length 16 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.567: Received command SET_KEEP_ALIVE 0 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.567: Keep alive toggled: 0 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.568: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.568: Got instructions of length 19 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.568: Received command SET_ENROLL_STAGES 5 280s (process:1999): libfprint-device-DEBUG: 17:02:38.568: Device reported close completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.568: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.568: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s Enroll done 280s ok 280s test_open_error (__main__.VirtualDeviceStorage.test_open_error) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.568: 114553135: ../libfprint/drivers/virtual-device.c:387 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.568: 114553142: ../libfprint/drivers/virtual-device-listener.c:153 280s (process:1999): libfprint-device-DEBUG: 17:02:38.568: Device reported open completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.568: Completing action FPI_DEVICE_ACTION_OPEN in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.568: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.568: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.568: Got instructions of length 16 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.568: Received command IGNORED_COMMAND 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.568: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.568: Got instructions of length 7 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.568: Received command ERROR 5 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.568: Processing command IGNORED_COMMAND 280s (process:1999): libfprint-device-DEBUG: 17:02:38.568: Device reported close completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.568: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.568: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.568: 114553653: ../libfprint/drivers/virtual-device.c:387 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.568: Processing command ERROR 5 280s (process:1999): libfprint-device-DEBUG: 17:02:38.568: Device reported open completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.568: Completing action FPI_DEVICE_ACTION_OPEN in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.568: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s ok 280s test_open_error_with_keep_alive (__main__.VirtualDeviceStorage.test_open_error_with_keep_alive) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.568: 114553766: ../libfprint/drivers/virtual-device.c:387 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.568: 114553772: ../libfprint/drivers/virtual-device-listener.c:153 280s (process:1999): libfprint-device-DEBUG: 17:02:38.568: Device reported open completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.568: Completing action FPI_DEVICE_ACTION_OPEN in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.568: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.569: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.569: Got instructions of length 16 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.569: Received command SET_KEEP_ALIVE 1 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.569: Keep alive toggled: 1 280s (process:1999): libfprint-device-DEBUG: 17:02:38.569: Device reported close completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.569: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.569: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.569: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.569: Got instructions of length 7 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.569: Received command ERROR 5 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.569: 114554089: ../libfprint/drivers/virtual-device.c:387 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.569: Processing command ERROR 5 280s (process:1999): libfprint-device-DEBUG: 17:02:38.569: Device reported open completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.569: Completing action FPI_DEVICE_ACTION_OPEN in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.569: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s ok 280s test_quick_enroll (__main__.VirtualDeviceStorage.test_quick_enroll) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.569: 114554205: ../libfprint/drivers/virtual-device.c:387 280s (process:1999): libfprint-device-DEBUG: 17:02:38.569: Device reported open completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.569: Completing action FPI_DEVICE_ACTION_OPEN in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.569: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.569: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.569: Got instructions of length 19 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.569: Received command SET_ENROLL_STAGES 1 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.569: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.569: Got instructions of length 14 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.569: Received command SCAN testprint 280s (process:1999): libfprint-device-DEBUG: 17:02:38.569: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.569: Processing command SCAN testprint 280s (process:1999): libfprint-device-DEBUG: 17:02:38.569: Device reported finger status change: FP_FINGER_STATUS_NEEDED 280s (process:1999): libfprint-device-DEBUG: 17:02:38.569: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 280s (process:1999): libfprint-device-DEBUG: 17:02:38.569: Device reported finger status change: FP_FINGER_STATUS_NEEDED 280s (process:1999): libfprint-device-DEBUG: 17:02:38.569: Device reported enroll progress, reported 1 of 1 have been completed 280s (process:1999): libfprint-device-DEBUG: 17:02:38.569: Device reported enroll completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.569: Device reported finger status change: FP_FINGER_STATUS_NONE 280s (process:1999): libfprint-device-DEBUG: 17:02:38.569: Print for finger FP_FINGER_LEFT_LITTLE enrolled 280s (process:1999): libfprint-device-DEBUG: 17:02:38.569: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.569: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.569: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.569: Got instructions of length 5 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.569: Received command CONT 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.569: Processing command CONT 280s (process:1999): libfprint-device-DEBUG: 17:02:38.569: Device reported deletion completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.569: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.569: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.569: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.569: Got instructions of length 16 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.569: Received command SET_KEEP_ALIVE 0 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.569: Keep alive toggled: 0 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.570: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.570: Got instructions of length 19 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.570: Received command SET_ENROLL_STAGES 5 280s (process:1999): libfprint-device-DEBUG: 17:02:38.570: Device reported close completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.570: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.570: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s Enroll done 280s ok 280s test_verify_missing_print (__main__.VirtualDeviceStorage.test_verify_missing_print) ... (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.570: 114555060: ../libfprint/drivers/virtual-device.c:387 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.570: 114555066: ../libfprint/drivers/virtual-device-listener.c:153 280s (process:1999): libfprint-device-DEBUG: 17:02:38.570: Device reported open completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.570: Completing action FPI_DEVICE_ACTION_OPEN in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.570: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.570: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.570: Got instructions of length 23 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.570: Received command SCAN not-existing-print 280s (process:1999): libfprint-device-DEBUG: 17:02:38.570: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.570: Processing command SCAN not-existing-print 280s (process:1999): libfprint-device-DEBUG: 17:02:38.570: Device reported finger status change: FP_FINGER_STATUS_NEEDED 280s (process:1999): libfprint-device-DEBUG: 17:02:38.570: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.570: Virtual device scanned print not-existing-print 280s (process:1999): libfprint-device-DEBUG: 17:02:38.570: Device reported verify result 280s (process:1999): libfprint-device-DEBUG: 17:02:38.570: Device reported finger status change: FP_FINGER_STATUS_NEEDED 280s (process:1999): libfprint-device-DEBUG: 17:02:38.570: Device reported verify completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.570: Device reported finger status change: FP_FINGER_STATUS_NONE 280s (process:1999): libfprint-device-DEBUG: 17:02:38.570: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.570: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.570: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.570: Got instructions of length 5 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.570: Received command CONT 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.570: Processing command CONT 280s (process:1999): libfprint-device-DEBUG: 17:02:38.570: Device reported deletion completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.570: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.570: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.570: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.570: Got instructions of length 16 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.570: Received command SET_KEEP_ALIVE 0 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.570: Keep alive toggled: 0 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.570: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.570: Got instructions of length 19 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.570: Received command SET_ENROLL_STAGES 5 280s (process:1999): libfprint-device-DEBUG: 17:02:38.570: Device reported close completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.570: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.570: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 280s ok 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.571: 114555912: ../libfprint/drivers/virtual-device.c:752 280s test_device_unplug (__main__.VirtualDeviceUnplugging.test_device_unplug) ... (process:1999): libfprint-context-DEBUG: 17:02:38.571: Initializing FpContext (libfprint version 1.94.7+tod1) 280s (process:1999): libfprint-tod-DEBUG: 17:02:38.571: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 280s (process:1999): libfprint-context-DEBUG: 17:02:38.572: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-5bzc7jwx/virtual-device.socket 280s (process:1999): libfprint-context-DEBUG: 17:02:38.572: created 280s (process:1999): libfprint-context-DEBUG: 17:02:38.572: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-pqcq12qf/virtual-device-storage.socket 280s (process:1999): libfprint-context-DEBUG: 17:02:38.572: created 280s (process:1999): libfprint-device-DEBUG: 17:02:38.572: Device reported probe completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.572: Device reported probe completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.572: Completing action FPI_DEVICE_ACTION_PROBE in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.572: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 280s (process:1999): libfprint-device-DEBUG: 17:02:38.572: Completing action FPI_DEVICE_ACTION_PROBE in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.572: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.572: 114557771: ../libfprint/drivers/virtual-device.c:387 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.572: 114557812: ../libfprint/drivers/virtual-device-listener.c:153 280s (process:1999): libfprint-device-DEBUG: 17:02:38.572: Device reported open completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.573: Completing action FPI_DEVICE_ACTION_OPEN in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.573: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.573: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.573: Got instructions of length 7 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.573: Received command UNPLUG 280s (process:1999): libfprint-device-DEBUG: 17:02:38.573: Device reported close completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.573: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.573: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.573: 114558609: ../libfprint/drivers/virtual-device.c:752 280s (process:1999): libfprint-virtual_device_storage-DEBUG: 17:02:38.573: 114558663: ../libfprint/drivers/virtual-device-storage.c:253 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.573: 114558701: ../libfprint/drivers/virtual-device.c:752 280s ok 280s test_device_unplug_during_verify (__main__.VirtualDeviceUnplugging.test_device_unplug_during_verify) ... (process:1999): libfprint-context-DEBUG: 17:02:38.574: Initializing FpContext (libfprint version 1.94.7+tod1) 280s (process:1999): libfprint-tod-DEBUG: 17:02:38.574: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 280s (process:1999): libfprint-context-DEBUG: 17:02:38.574: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-5bzc7jwx/virtual-device.socket 280s (process:1999): libfprint-context-DEBUG: 17:02:38.574: created 280s (process:1999): libfprint-context-DEBUG: 17:02:38.574: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-pqcq12qf/virtual-device-storage.socket 280s (process:1999): libfprint-context-DEBUG: 17:02:38.574: created 280s (process:1999): libfprint-device-DEBUG: 17:02:38.574: Device reported probe completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.574: Device reported probe completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.574: Completing action FPI_DEVICE_ACTION_PROBE in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.574: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 280s (process:1999): libfprint-device-DEBUG: 17:02:38.574: Completing action FPI_DEVICE_ACTION_PROBE in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.574: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.574: 114559879: ../libfprint/drivers/virtual-device.c:387 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.575: 114559920: ../libfprint/drivers/virtual-device-listener.c:153 280s (process:1999): libfprint-device-DEBUG: 17:02:38.575: Device reported open completion 280s (process:1999): libfprint-device-DEBUG: 17:02:38.575: Completing action FPI_DEVICE_ACTION_OPEN in idle! 280s (process:1999): libfprint-device-DEBUG: 17:02:38.575: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 280s (process:1999): libfprint-device-DEBUG: 17:02:38.575: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 280s (process:1999): libfprint-device-DEBUG: 17:02:38.575: Device reported finger status change: FP_FINGER_STATUS_NEEDED 280s (process:1999): libfprint-virtual_device_connection-DEBUG: 17:02:38.575: Got a new connection! 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.575: Got instructions of length 7 280s (process:1999): libfprint-virtual_device-DEBUG: 17:02:38.575: Received command UNPLUG 280s (process:1999): libfprint-device-DEBUG: 17:02:38.675: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 281s (process:1999): libfprint-device-DEBUG: 17:02:39.076: Device reported generic error (No commands arrived in time to run!) during action; action was: FPI_DEVICE_ACTION_VERIFY 281s (process:1999): libfprint-device-DEBUG: 17:02:39.076: Device reported verify completion 281s (process:1999): libfprint-device-DEBUG: 17:02:39.076: Device reported finger status change: FP_FINGER_STATUS_NONE 281s (process:1999): libfprint-device-DEBUG: 17:02:39.076: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 281s (process:1999): libfprint-device-DEBUG: 17:02:39.076: Updated temperature model after 0.40 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 281s (process:1999): libfprint-device-DEBUG: 17:02:39.077: Device reported close completion 281s (process:1999): libfprint-device-DEBUG: 17:02:39.077: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 281s (process:1999): libfprint-device-DEBUG: 17:02:39.077: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 281s (process:1999): libfprint-virtual_device-DEBUG: 17:02:39.077: 115062241: ../libfprint/drivers/virtual-device.c:752 281s (process:1999): libfprint-virtual_device_storage-DEBUG: 17:02:39.077: 115062261: ../libfprint/drivers/virtual-device-storage.c:253 281s (process:1999): libfprint-virtual_device-DEBUG: 17:02:39.077: 115062266: ../libfprint/drivers/virtual-device.c:752 281s ok 281s 281s ---------------------------------------------------------------------- 281s Ran 86 tests in 17.526s 281s 281s OK (skipped=1) 281s PASS: libfprint-2/virtual-device.test 281s Running test: libfprint-2/driver-egismoc.test 281s ** (umockdev-run:2017): DEBUG: 17:02:39.130: umockdev.vala:123: Created udev test bed /tmp/umockdev.E8ZAK2 281s ** (umockdev-run:2017): DEBUG: 17:02:39.130: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-5 281s ** (umockdev-run:2017): DEBUG: 17:02:39.131: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-5 (subsystem usb) 281s ** (umockdev-run:2017): DEBUG: 17:02:39.134: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.E8ZAK2/dev/bus/usb/003/012 281s ** (umockdev-run:2017): DEBUG: 17:02:39.134: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3 281s ** (umockdev-run:2017): DEBUG: 17:02:39.135: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb) 281s ** (umockdev-run:2017): DEBUG: 17:02:39.137: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.E8ZAK2/dev/bus/usb/003/001 281s ** (umockdev-run:2017): DEBUG: 17:02:39.137: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 281s ** (umockdev-run:2017): DEBUG: 17:02:39.137: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 281s (process:2021): libfprint-context-DEBUG: 17:02:39.184: Initializing FpContext (libfprint version 1.94.7+tod1) 281s (process:2021): libfprint-tod-DEBUG: 17:02:39.184: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.186: 115171316: ../libfprint/drivers/egismoc/egismoc.c:1515 281s (process:2021): libfprint-context-DEBUG: 17:02:39.186: No driver found for USB device 1D6B:0002 281s (process:2021): libfprint-device-DEBUG: 17:02:39.186: Device reported probe completion 281s (process:2021): libfprint-device-DEBUG: 17:02:39.186: Completing action FPI_DEVICE_ACTION_PROBE in idle! 281s (process:2021): libfprint-device-DEBUG: 17:02:39.187: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find ha(process:2021): libfprint-egismoc-DEBUG: 17:02:39.189: Opening device 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.190: [egismoc] DEV_INIT_STATES entering state 0 281s ndle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s libusb: error [op_handle_events] cannot find handle for fd 9 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.190: [egismoc] DEV_INIT_STATES entering state 1 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.191: [egismoc] DEV_INIT_STATES entering state 2 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.191: [egismoc] DEV_INIT_STATES entering state 3 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.192: [egismoc] DEV_INIT_STATES entering state 4 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.192: [egismoc] DEV_INIT_STATES entering state 5 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.192: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.192: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.192: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.193: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.193: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.193: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.193: Firmware version callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.193: Response suffix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.193: Device firmware version is 9050.1.1.81 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.193: [egismoc] DEV_INIT_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.193: Task SSM done 281s (process:2021): libfprint-device-DEBUG: 17:02:39.193: Device reported open completion 281s (process:2021): libfprint-device-DEBUG: 17:02:39.193: Completing action FPI_DEVICE_ACTION_OPEN in idle! 281s (process:2021): libfprint-device-DEBUG: 17:02:39.193: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.193: List 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.193: [egismoc] LIST_STATES entering state 0 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.193: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.193: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.193: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.194: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.194: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.194: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.194: List callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.194: Device fingerprint 0: FP1-20231016-1-AAA9163E-root 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.194: Device fingerprint 1: FP1-20231016-2-5102A0A3-root 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.194: Device fingerprint 2: FP1-20231016-3-5159A026-root 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.194: Device fingerprint 3: FP1-20231016-4-A25C1212-root 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.194: Device fingerprint 4: FP1-20231016-5-EC893AA9-root 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.194: Device fingerprint 5: \u0006\u001d\xcbc$ir%\xa22U֨\o\xff\x8ddY\x84\u0003\xbac\xcfO\xde\xc2!L\u001eN( 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.194: Device fingerprint 6: \xd7pܖsT3\xf6>\xd9\u0002"/[\xf8\u0017Iqpz\u000c\xfa,M\xdfm5\u007fq\xc6\xdew 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.194: Number of currently enrolled fingerprints on the device is 7 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.194: [egismoc] LIST_STATES entering state 1 281s (process:2021): libfprint-device-DEBUG: 17:02:39.194: Device reported listing completion 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.194: [egismoc] LIST_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.194: Task SSM done 281s (process:2021): libfprint-device-DEBUG: 17:02:39.194: Completing action FPI_DEVICE_ACTION_LIST in idle! 281s (process:2021): libfprint-device-DEBUG: 17:02:39.194: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.194: Clear storage 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.194: [egismoc] DELETE_STATES entering state 0 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.194: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.194: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.194: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.195: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.196: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.196: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.196: List callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.196: Device fingerprint 0: FP1-20231016-1-AAA9163E-root 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.196: Device fingerprint 1: FP1-20231016-2-5102A0A3-root 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.196: Device fingerprint 2: FP1-20231016-3-5159A026-root 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.196: Device fingerprint 3: FP1-20231016-4-A25C1212-root 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.196: Device fingerprint 4: FP1-20231016-5-EC893AA9-root 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.196: Device fingerprint 5: \u0006\u001d\xcbc$ir%\xa22U֨\o\xff\x8ddY\x84\u0003\xbac\xcfO\xde\xc2!L\u001eN( 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.196: Device fingerprint 6: \xd7pܖsT3\xf6>\xd9\u0002"/[\xf8\u0017Iqpz\u000c\xfa,M\xdfm5\u007fq\xc6\xdew 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.196: Number of currently enrolled fingerprints on the device is 7 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.196: [egismoc] DELETE_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.196: Get delete command 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.196: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.196: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.196: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.196: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.196: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.197: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.197: Delete callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.197: Response prefix valid: yes 281s (process:2021): libfprint-device-DEBUG: 17:02:39.197: Device reported deletion completion 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.197: [egismoc] DELETE_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.197: Task SSM done 281s (process:2021): libfprint-device-DEBUG: 17:02:39.197: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 281s (process:2021): libfprint-device-DEBUG: 17:02:39.197: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.197: List 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.197: [egismoc] LIST_STATES entering state 0 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.197: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.197: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.197: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.197: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.198: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.198: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.198: List callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.198: Number of currently enrolled fingerprints on the device is 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.198: [egismoc] LIST_STATES entering state 1 281s (process:2021): libfprint-device-DEBUG: 17:02:39.198: Device reported listing completion 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.198: [egismoc] LIST_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.198: Task SSM done 281s (process:2021): libfprint-device-DEBUG: 17:02:39.198: Completing action FPI_DEVICE_ACTION_LIST in idle! 281s (process:2021): libfprint-device-DEBUG: 17:02:39.198: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 281s (process:2021): libfprint-device-DEBUG: 17:02:39.198: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.198: Enroll 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.198: [egismoc] ENROLL_STATES entering state 0 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.198: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.198: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.198: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.199: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.199: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.199: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.199: List callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.199: Number of currently enrolled fingerprints on the device is 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.199: [egismoc] ENROLL_STATES entering state 1 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.199: [egismoc] ENROLL_STATES entering state 2 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.199: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.199: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.199: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.199: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.200: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.200: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.200: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.200: [egismoc] ENROLL_STATES entering state 3 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.200: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.200: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.200: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.200: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.201: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.201: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.201: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.201: [egismoc] ENROLL_STATES entering state 4 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.201: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.201: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.201: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.201: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.201: [egismoc] ENROLL_STATES entering state 5 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.201: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.201: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.201: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.202: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.202: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.202: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.202: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.202: [egismoc] ENROLL_STATES entering state 6 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.202: Get check command 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.202: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.202: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.202: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.202: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.203: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.203: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.203: Enroll check callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.203: Response suffix valid: yes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.203: [egismoc] ENROLL_STATES entering state 7 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.203: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.203: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.203: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.203: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.204: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.204: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.204: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.204: [egismoc] ENROLL_STATES entering state 8 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.204: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.204: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.204: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.204: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.205: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.205: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.205: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.205: [egismoc] ENROLL_STATES entering state 9 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.205: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.205: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.205: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.205: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.206: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.206: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.206: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.206: [egismoc] ENROLL_STATES entering state 10 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.206: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.206: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.206: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.206: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.206: [egismoc] ENROLL_STATES entering state 11 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.206: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.206: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.206: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.206: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.207: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.207: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.207: Read capture callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.207: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.207: Response suffix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.207: Partial capture successful. Please touch the sensor again (1/10) 281s (process:2021): libfprint-device-DEBUG: 17:02:39.207: Device reported enroll progress, reported 1 of 10 have been completed 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.207: [egismoc] ENROLL_STATES entering state 8 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.207: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.207: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.207: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.207: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.208: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.208: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.208: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.208: [egismoc] ENROLL_STATES entering state 9 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.208: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.208: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.208: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.208: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.209: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.209: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.209: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.209: [egismoc] ENROLL_STATES entering state 10 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.209: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.209: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.209: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.209: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.209: [egismoc] ENROLL_STATES entering state 11 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.209: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.209: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.209: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.210: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.210: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.210: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.210: Read capture callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.210: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.210: Response suffix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.210: Partial capture successful. Please touch the sensor again (2/10) 281s (process:2021): libfprint-device-DEBUG: 17:02:39.210: Device reported enroll progress, reported 2 of 10 have been completed 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.210: [egismoc] ENROLL_STATES entering state 8 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.210: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.210: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.210: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.211: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.211: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.211: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.211: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.211: [egismoc] ENROLL_STATES entering state 9 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.211: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.211: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.211: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.212: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.212: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.212: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.212: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.212: [egismoc] ENROLL_STATES entering state 10 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.212: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.212: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.213: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.213: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.213: [egismoc] ENROLL_STATES entering state 11 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.213: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.213: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.213: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.213: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.213: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.213: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.213: Read capture callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.213: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.213: Response suffix valid: NO 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.213: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.213: Response suffix valid: yes 281s (process:2021): libfprint-device-DEBUG: 17:02:39.213: Device reported enroll progress, reported 2 of 10 have been completed 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.213: [egismoc] ENROLL_STATES entering state 8 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.213: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.213: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.213: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.214: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.214: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.214: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.214: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.214: [egismoc] ENROLL_STATES entering state 9 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.214: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.214: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.214: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.215: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.215: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.215: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.215: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.215: [egismoc] ENROLL_STATES entering state 10 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.215: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.215: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.216: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.216: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.216: [egismoc] ENROLL_STATES entering state 11 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.216: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.216: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.216: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.216: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.217: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.217: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.217: Read capture callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.217: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.217: Response suffix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.217: Partial capture successful. Please touch the sensor again (3/10) 281s (process:2021): libfprint-device-DEBUG: 17:02:39.217: Device reported enroll progress, reported 3 of 10 have been completed 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.217: [egismoc] ENROLL_STATES entering state 8 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.217: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.217: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.217: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.217: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.218: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.218: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.218: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.218: [egismoc] ENROLL_STATES entering state 9 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.218: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.218: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.218: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.218: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.218: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.218: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.218: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.218: [egismoc] ENROLL_STATES entering state 10 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.218: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.218: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.219: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.219: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.219: [egismoc] ENROLL_STATES entering state 11 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.219: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.219: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.219: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.219: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.220: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.220: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.220: Read capture callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.220: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.220: Response suffix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.220: Partial capture successful. Please touch the sensor again (4/10) 281s (process:2021): libfprint-device-DEBUG: 17:02:39.220: Device reported enroll progress, reported 4 of 10 have been completed 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.220: [egismoc] ENROLL_STATES entering state 8 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.220: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.220: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.220: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.220: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.221: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.221: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.221: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.221: [egismoc] ENROLL_STATES entering state 9 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.221: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.221: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.221: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.221: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.222: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.222: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.222: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.222: [egismoc] ENROLL_STATES entering state 10 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.222: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.222: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.222: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.222: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.222: [egismoc] ENROLL_STATES entering state 11 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.222: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.222: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.222: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.223: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.223: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.223: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.223: Read capture callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.223: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.223: Response suffix valid: NO 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.223: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.223: Response suffix valid: yes 281s (process:2021): libfprint-device-DEBUG: 17:02:39.223: Device reported enroll progress, reported 4 of 10 have been completed 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.223: [egismoc] ENROLL_STATES entering state 8 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.223: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.223: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.223: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.224: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.224: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.224: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.224: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.224: [egismoc] ENROLL_STATES entering state 9 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.224: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.224: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.224: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.225: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.225: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.225: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.225: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.225: [egismoc] ENROLL_STATES entering state 10 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.225: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.225: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.225: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.225: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.225: [egismoc] ENROLL_STATES entering state 11 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.225: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.225: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.225: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.226: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.226: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.226: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.226: Read capture callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.226: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.226: Response suffix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.226: Partial capture successful. Please touch the sensor again (5/10) 281s (process:2021): libfprint-device-DEBUG: 17:02:39.226: Device reported enroll progress, reported 5 of 10 have been completed 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.226: [egismoc] ENROLL_STATES entering state 8 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.226: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.226: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.226: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.227: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.227: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.227: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.227: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.227: [egismoc] ENROLL_STATES entering state 9 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.227: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.227: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.227: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.228: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.228: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.228: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.228: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.228: [egismoc] ENROLL_STATES entering state 10 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.228: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.228: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.228: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.228: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.228: [egismoc] ENROLL_STATES entering state 11 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.228: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.228: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.228: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.229: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.229: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.229: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.229: Read capture callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.229: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.229: Response suffix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.229: Partial capture successful. Please touch the sensor again (6/10) 281s (process:2021): libfprint-device-DEBUG: 17:02:39.229: Device reported enroll progress, reported 6 of 10 have been completed 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.229: [egismoc] ENROLL_STATES entering state 8 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.229: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.229: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.229: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.230: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.230: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.230: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.230: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.230: [egismoc] ENROLL_STATES entering state 9 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.230: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.230: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.230: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.231: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.231: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.231: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.231: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.231: [egismoc] ENROLL_STATES entering state 10 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.231: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.231: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.232: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.232: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.232: [egismoc] ENROLL_STATES entering state 11 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.232: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.232: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.232: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.232: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.233: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.233: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.233: Read capture callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.233: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.233: Response suffix valid: NO 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.233: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.233: Response suffix valid: yes 281s (process:2021): libfprint-device-DEBUG: 17:02:39.233: Device reported enroll progress, reported 6 of 10 have been completed 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.233: [egismoc] ENROLL_STATES entering state 8 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.233: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.233: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.233: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.233: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.234: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.234: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.234: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.234: [egismoc] ENROLL_STATES entering state 9 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.234: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.234: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.234: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.234: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.234: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.234: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.234: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.234: [egismoc] ENROLL_STATES entering state 10 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.234: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.234: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.235: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.235: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.235: [egismoc] ENROLL_STATES entering state 11 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.235: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.235: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.235: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.235: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.236: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.236: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.236: Read capture callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.236: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.236: Response suffix valid: NO 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.236: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.236: Response suffix valid: yes 281s (process:2021): libfprint-device-DEBUG: 17:02:39.236: Device reported enroll progress, reported 6 of 10 have been completed 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.236: [egismoc] ENROLL_STATES entering state 8 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.236: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.236: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.236: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.236: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.237: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.237: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.237: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.237: [egismoc] ENROLL_STATES entering state 9 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.237: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.237: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.237: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.237: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.238: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.238: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.238: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.238: [egismoc] ENROLL_STATES entering state 10 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.238: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.238: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.238: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.238: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.238: [egismoc] ENROLL_STATES entering state 11 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.238: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.238: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.238: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.238: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.239: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.239: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.239: Read capture callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.239: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.239: Response suffix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.239: Partial capture successful. Please touch the sensor again (7/10) 281s (process:2021): libfprint-device-DEBUG: 17:02:39.239: Device reported enroll progress, reported 7 of 10 have been completed 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.239: [egismoc] ENROLL_STATES entering state 8 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.239: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.239: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.239: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.239: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.240: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.240: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.240: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.240: [egismoc] ENROLL_STATES entering state 9 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.240: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.240: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.240: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.240: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.241: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.241: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.241: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.241: [egismoc] ENROLL_STATES entering state 10 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.241: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.241: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.241: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.241: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.241: [egismoc] ENROLL_STATES entering state 11 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.241: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.241: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.241: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.242: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.242: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.242: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.242: Read capture callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.242: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.242: Response suffix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.242: Partial capture successful. Please touch the sensor again (8/10) 281s (process:2021): libfprint-device-DEBUG: 17:02:39.242: Device reported enroll progress, reported 8 of 10 have been completed 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.242: [egismoc] ENROLL_STATES entering state 8 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.242: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.242: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.242: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.243: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.243: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.243: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.243: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.243: [egismoc] ENROLL_STATES entering state 9 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.243: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.243: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.243: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.243: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.244: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.244: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.244: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.244: [egismoc] ENROLL_STATES entering state 10 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.244: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.244: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.244: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.244: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.244: [egismoc] ENROLL_STATES entering state 11 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.244: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.244: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.244: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.245: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.245: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.245: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.245: Read capture callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.245: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.245: Response suffix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.245: Partial capture successful. Please touch the sensor again (9/10) 281s (process:2021): libfprint-device-DEBUG: 17:02:39.245: Device reported enroll progress, reported 9 of 10 have been completed 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.245: [egismoc] ENROLL_STATES entering state 8 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.245: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.245: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.245: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.246: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.246: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.246: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.246: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.246: [egismoc] ENROLL_STATES entering state 9 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.246: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.246: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.246: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.247: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.247: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.247: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.247: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.247: [egismoc] ENROLL_STATES entering state 10 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.247: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.247: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.247: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.247: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.247: [egismoc] ENROLL_STATES entering state 11 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.247: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.247: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.247: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.248: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.248: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.248: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.248: Read capture callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.248: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.248: Response suffix valid: NO 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.248: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.248: Response suffix valid: yes 281s (process:2021): libfprint-device-DEBUG: 17:02:39.248: Device reported enroll progress, reported 9 of 10 have been completed 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.248: [egismoc] ENROLL_STATES entering state 8 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.248: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.248: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.248: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.249: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.249: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.249: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.249: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.249: [egismoc] ENROLL_STATES entering state 9 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.249: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.249: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.249: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.250: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.250: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.250: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.250: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.250: [egismoc] ENROLL_STATES entering state 10 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.250: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.250: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.251: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.251: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.251: [egismoc] ENROLL_STATES entering state 11 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.251: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.251: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.251: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.251: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.252: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.252: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.252: Read capture callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.252: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.252: Response suffix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.252: Partial capture successful. Please touch the sensor again (10/10) 281s (process:2021): libfprint-device-DEBUG: 17:02:39.252: Device reported enroll progress, reported 10 of 10 have been completed 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.252: [egismoc] ENROLL_STATES entering state 12 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.252: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.252: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.252: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.252: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.253: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.253: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.253: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.253: [egismoc] ENROLL_STATES entering state 13 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.253: New fingerprint ID: FP1-00000000-2-00000000-nobody 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.253: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.253: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.253: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.253: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.253: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.254: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.254: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.254: [egismoc] ENROLL_STATES entering state 14 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.254: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.254: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.254: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.254: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.254: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.254: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.254: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.254: [egismoc] ENROLL_STATES entering state 15 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.254: Enrollment was successful! 281s (process:2021): libfprint-device-DEBUG: 17:02:39.254: Device reported enroll completion 281s (process:2021): libfprint-device-DEBUG: 17:02:39.254: Device reported finger status change: FP_FINGER_STATUS_NONE 281s (process:2021): libfprint-device-DEBUG: 17:02:39.254: Print for finger FP_FINGER_LEFT_INDEX enrolled 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.254: [egismoc] ENROLL_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.254: Task SSM done 281s (process:2021): libfprint-device-DEBUG: 17:02:39.254: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 281s (process:2021): libfprint-device-DEBUG: 17:02:39.254: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.254: List 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.255: [egismoc] LIST_STATES entering state 0 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.255: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.255: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.255: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.255: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.256: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.256: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.256: List callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.256: Device fingerprint 0: FP1-00000000-2-00000000-nobody 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.256: Number of currently enrolled fingerprints on the device is 1 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.256: [egismoc] LIST_STATES entering state 1 281s (process:2021): libfprint-device-DEBUG: 17:02:39.256: Device reported listing completion 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.256: [egismoc] LIST_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.256: Task SSM done 281s (process:2021): libfprint-device-DEBUG: 17:02:39.256: Completing action FPI_DEVICE_ACTION_LIST in idle! 281s (process:2021): libfprint-device-DEBUG: 17:02:39.256: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 281s (process:2021): libfprint-device-DEBUG: 17:02:39.256: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.256: Identify or Verify 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.256: [egismoc] IDENTIFY_STATES entering state 0 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.256: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.256: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.256: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.256: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.257: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.257: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.257: List callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.257: Device fingerprint 0: FP1-00000000-2-00000000-nobody 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.257: Number of currently enrolled fingerprints on the device is 1 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.257: [egismoc] IDENTIFY_STATES entering state 1 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.257: [egismoc] IDENTIFY_STATES entering state 2 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.257: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.257: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.257: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.257: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.258: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.258: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.258: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.258: [egismoc] IDENTIFY_STATES entering state 3 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.258: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.258: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.258: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.258: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.258: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.258: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.258: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.258: [egismoc] IDENTIFY_STATES entering state 4 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.258: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.258: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.259: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.259: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.259: [egismoc] IDENTIFY_STATES entering state 5 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.259: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.259: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.259: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.259: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.260: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.260: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.260: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.260: [egismoc] IDENTIFY_STATES entering state 6 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.260: Get check command 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.260: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.260: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.260: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.260: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.261: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.261: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.261: Identify check callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.261: Response suffix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.261: Identify successful for: FP1-00000000-2-00000000-nobody 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.261: Verifying against: FP1-00000000-2-00000000-nobody 281s (process:2021): libfprint-device-DEBUG: 17:02:39.261: Device reported verify result 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.261: [egismoc] IDENTIFY_STATES entering state 7 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.261: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.261: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.261: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.261: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.262: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.262: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.262: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.262: [egismoc] IDENTIFY_STATES entering state 8 281s (process:2021): libfprint-device-DEBUG: 17:02:39.262: Device reported verify completion 281s (process:2021): libfprint-device-DEBUG: 17:02:39.262: Device reported finger status change: FP_FINGER_STATUS_NONE 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.262: [egismoc] IDENTIFY_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.262: Task SSM done 281s (process:2021): libfprint-device-DEBUG: 17:02:39.262: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 281s (process:2021): libfprint-device-DEBUG: 17:02:39.262: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 281s (process:2021): libfprint-device-DEBUG: 17:02:39.262: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.262: Identify or Verify 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.262: [egismoc] IDENTIFY_STATES entering state 0 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.262: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.262: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.262: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.262: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.263: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.263: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.263: List callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.263: Device fingerprint 0: FP1-00000000-2-00000000-nobody 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.263: Number of currently enrolled fingerprints on the device is 1 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.263: [egismoc] IDENTIFY_STATES entering state 1 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.263: [egismoc] IDENTIFY_STATES entering state 2 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.263: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.263: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.263: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.263: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.264: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.264: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.264: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.264: [egismoc] IDENTIFY_STATES entering state 3 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.264: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.264: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.264: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.264: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.265: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.265: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.265: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.265: [egismoc] IDENTIFY_STATES entering state 4 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.265: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.265: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.265: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.265: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.265: [egismoc] IDENTIFY_STATES entering state 5 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.265: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.265: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.265: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.266: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.266: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.266: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.266: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.266: [egismoc] IDENTIFY_STATES entering state 6 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.266: Get check command 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.266: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.266: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.266: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.267: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.267: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.267: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.267: Identify check callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.267: Response suffix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.267: Identify successful for: FP1-00000000-2-00000000-nobody 281s (process:2021): libfprint-device-DEBUG: 17:02:39.267: Device reported identify result 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.267: [egismoc] IDENTIFY_STATES entering state 7 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.267: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.267: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.267: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.268: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.268: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.268: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.268: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.268: [egismoc] IDENTIFY_STATES entering state 8 281s (process:2021): libfprint-device-DEBUG: 17:02:39.268: Device reported identify completion 281s (process:2021): libfprint-device-DEBUG: 17:02:39.268: Device reported finger status change: FP_FINGER_STATUS_NONE 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.268: [egismoc] IDENTIFY_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.268: Task SSM done 281s (process:2021): libfprint-device-DEBUG: 17:02:39.268: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 281s (process:2021): libfprint-device-DEBUG: 17:02:39.268: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 281s (process:2021): libfprint-device-DEBUG: 17:02:39.268: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.268: Enroll 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.268: [egismoc] ENROLL_STATES entering state 0 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.268: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.268: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.268: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.269: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.269: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.269: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.269: List callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.269: Device fingerprint 0: FP1-00000000-2-00000000-nobody 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.269: Number of currently enrolled fingerprints on the device is 1 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.269: [egismoc] ENROLL_STATES entering state 1 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.269: [egismoc] ENROLL_STATES entering state 2 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.269: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.269: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.269: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.270: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.270: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.270: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.270: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.270: [egismoc] ENROLL_STATES entering state 3 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.270: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.270: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.270: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.271: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.271: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.271: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.271: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.271: [egismoc] ENROLL_STATES entering state 4 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.271: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.271: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.271: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.271: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.271: [egismoc] ENROLL_STATES entering state 5 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.271: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.271: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.271: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.272: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.272: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.272: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.272: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.272: [egismoc] ENROLL_STATES entering state 6 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.272: Get check command 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.272: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.272: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.272: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.273: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.273: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.273: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.273: Enroll check callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.273: Response suffix valid: NO 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.273: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.273: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.273: Task SSM done 281s (process:2021): libfprint-device-DEBUG: 17:02:39.273: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 281s (process:2021): libfprint-device-DEBUG: 17:02:39.273: Device reported enroll completion 281s (process:2021): libfprint-device-DEBUG: 17:02:39.273: Device reported finger status change: FP_FINGER_STATUS_NONE 281s (process:2021): libfprint-device-DEBUG: 17:02:39.273: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 281s (process:2021): libfprint-device-DEBUG: 17:02:39.273: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.274: List 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.274: [egismoc] LIST_STATES entering state 0 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.274: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.274: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.274: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.274: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.274: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.274: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.274: List callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.274: Device fingerprint 0: FP1-00000000-2-00000000-nobody 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.274: Number of currently enrolled fingerprints on the device is 1 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.274: [egismoc] LIST_STATES entering state 1 281s (process:2021): libfprint-device-DEBUG: 17:02:39.274: Device reported listing completion 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.274: [egismoc] LIST_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.274: Task SSM done 281s (process:2021): libfprint-device-DEBUG: 17:02:39.274: Completing action FPI_DEVICE_ACTION_LIST in idle! 281s (process:2021): libfprint-device-DEBUG: 17:02:39.274: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 281s (process:2021): libfprint-device-DEBUG: 17:02:39.275: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.275: Enroll 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.275: [egismoc] ENROLL_STATES entering state 0 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.275: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.275: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.275: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.275: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.275: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.276: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.276: List callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.276: Device fingerprint 0: FP1-00000000-2-00000000-nobody 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.276: Number of currently enrolled fingerprints on the device is 1 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.276: [egismoc] ENROLL_STATES entering state 1 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.276: [egismoc] ENROLL_STATES entering state 2 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.276: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.276: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.276: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.276: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.276: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.276: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.276: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.276: [egismoc] ENROLL_STATES entering state 3 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.276: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.276: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.276: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.277: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.277: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.277: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.277: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.277: [egismoc] ENROLL_STATES entering state 4 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.277: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.277: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.278: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.278: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.278: [egismoc] ENROLL_STATES entering state 5 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.278: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.278: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.278: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.278: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.279: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.279: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.279: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.279: [egismoc] ENROLL_STATES entering state 6 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.279: Get check command 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.279: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.279: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.279: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.279: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.280: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.280: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.280: Enroll check callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.280: Response suffix valid: yes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.280: [egismoc] ENROLL_STATES entering state 7 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.280: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.280: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.280: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.280: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.280: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.280: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.280: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.280: [egismoc] ENROLL_STATES entering state 8 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.280: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.280: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.280: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.281: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.281: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.281: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.281: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.281: [egismoc] ENROLL_STATES entering state 9 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.281: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.281: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.281: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.282: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.282: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.282: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.282: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.282: [egismoc] ENROLL_STATES entering state 10 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.282: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.282: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.283: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.283: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.283: [egismoc] ENROLL_STATES entering state 11 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.283: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.283: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.283: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.283: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.283: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.283: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.283: Read capture callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.283: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.283: Response suffix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.283: Partial capture successful. Please touch the sensor again (1/10) 281s (process:2021): libfprint-device-DEBUG: 17:02:39.283: Device reported enroll progress, reported 1 of 10 have been completed 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.284: [egismoc] ENROLL_STATES entering state 8 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.284: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.284: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.284: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.284: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.284: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.284: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.284: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.284: [egismoc] ENROLL_STATES entering state 9 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.284: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.284: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.284: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.285: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.285: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.285: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.285: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.285: [egismoc] ENROLL_STATES entering state 10 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.285: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.285: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.286: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.286: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.286: [egismoc] ENROLL_STATES entering state 11 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.286: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.286: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.286: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.286: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.287: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.287: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.287: Read capture callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.287: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.287: Response suffix valid: NO 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.287: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.287: Response suffix valid: yes 281s (process:2021): libfprint-device-DEBUG: 17:02:39.287: Device reported enroll progress, reported 1 of 10 have been completed 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.287: [egismoc] ENROLL_STATES entering state 8 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.287: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.287: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.287: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.287: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.288: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.288: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.288: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.288: [egismoc] ENROLL_STATES entering state 9 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.288: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.288: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.288: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.288: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.289: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.289: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.289: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.289: [egismoc] ENROLL_STATES entering state 10 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.289: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.289: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.289: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.289: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.289: [egismoc] ENROLL_STATES entering state 11 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.289: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.289: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.289: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.289: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.290: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.290: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.290: Read capture callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.290: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.290: Response suffix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.290: Partial capture successful. Please touch the sensor again (2/10) 281s (process:2021): libfprint-device-DEBUG: 17:02:39.290: Device reported enroll progress, reported 2 of 10 have been completed 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.290: [egismoc] ENROLL_STATES entering state 8 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.290: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.290: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.290: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.290: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.291: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.291: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.291: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.291: [egismoc] ENROLL_STATES entering state 9 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.291: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.291: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.291: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.291: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.292: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.292: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.292: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.292: [egismoc] ENROLL_STATES entering state 10 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.292: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.292: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.292: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.292: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.292: [egismoc] ENROLL_STATES entering state 11 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.292: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.292: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.292: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.293: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.293: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.293: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.293: Read capture callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.293: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.293: Response suffix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.293: Partial capture successful. Please touch the sensor again (3/10) 281s (process:2021): libfprint-device-DEBUG: 17:02:39.293: Device reported enroll progress, reported 3 of 10 have been completed 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.293: [egismoc] ENROLL_STATES entering state 8 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.293: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.293: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.293: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.293: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.294: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.294: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.294: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.294: [egismoc] ENROLL_STATES entering state 9 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.294: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.294: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.294: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.294: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.295: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.295: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.295: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.295: [egismoc] ENROLL_STATES entering state 10 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.295: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.295: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.295: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.295: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.295: [egismoc] ENROLL_STATES entering state 11 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.295: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.295: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.295: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.296: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.296: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.296: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.296: Read capture callback 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.296: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.296: Response suffix valid: NO 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.296: Response prefix valid: yes 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.296: Response suffix valid: yes 281s (process:2021): libfprint-device-DEBUG: 17:02:39.296: Device reported enroll progress, reported 3 of 10 have been completed 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.296: [egismoc] ENROLL_STATES entering state 8 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.296: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.296: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.296: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.297: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.297: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.297: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.297: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.297: [egismoc] ENROLL_STATES entering state 9 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.297: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.297: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.297: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.297: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.298: Command receive callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.298: [egismoc] CMD_STATES completed successfully 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.298: Task SSM next state callback 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.298: [egismoc] ENROLL_STATES entering state 10 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.298: Wait for finger on sensor 281s (process:2021): libfprint-device-DEBUG: 17:02:39.298: Device reported finger status change: FP_FINGER_STATUS_NEEDED 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.298: Finger on sensor callback 281s (process:2021): libfprint-device-DEBUG: 17:02:39.298: Device reported finger status change: FP_FINGER_STATUS_PRESENT 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.298: [egismoc] ENROLL_STATES entering state 11 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.298: Execute command and get response 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.298: Get check bytes 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.298: [egismoc] CMD_STATES entering state 0 281s (process:2021): libfprint-SSM-DEBUG: 17:02:39.299: [egismoc] CMD_STATES entering state 1 281s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.299: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.299: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.299: Read capture callback 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.299: Response prefix valid: yes 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.299: Response suffix valid: NO 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.299: Response prefix valid: yes 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.299: Response suffix valid: yes 282s (process:2021): libfprint-device-DEBUG: 17:02:39.299: Device reported enroll progress, reported 3 of 10 have been completed 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.299: [egismoc] ENROLL_STATES entering state 8 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.299: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.299: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.299: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.300: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.300: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.300: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.300: Task SSM next state callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.300: [egismoc] ENROLL_STATES entering state 9 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.300: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.300: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.300: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.301: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.301: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.301: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.301: Task SSM next state callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.301: [egismoc] ENROLL_STATES entering state 10 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.301: Wait for finger on sensor 282s (process:2021): libfprint-device-DEBUG: 17:02:39.301: Device reported finger status change: FP_FINGER_STATUS_NEEDED 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.302: Finger on sensor callback 282s (process:2021): libfprint-device-DEBUG: 17:02:39.302: Device reported finger status change: FP_FINGER_STATUS_PRESENT 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.302: [egismoc] ENROLL_STATES entering state 11 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.302: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.302: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.302: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.302: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.303: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.303: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.303: Read capture callback 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.303: Response prefix valid: yes 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.303: Response suffix valid: yes 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.303: Partial capture successful. Please touch the sensor again (4/10) 282s (process:2021): libfprint-device-DEBUG: 17:02:39.303: Device reported enroll progress, reported 4 of 10 have been completed 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.303: [egismoc] ENROLL_STATES entering state 8 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.303: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.303: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.303: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.303: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.304: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.304: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.304: Task SSM next state callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.304: [egismoc] ENROLL_STATES entering state 9 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.304: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.304: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.304: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.304: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.305: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.305: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.305: Task SSM next state callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.305: [egismoc] ENROLL_STATES entering state 10 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.305: Wait for finger on sensor 282s (process:2021): libfprint-device-DEBUG: 17:02:39.305: Device reported finger status change: FP_FINGER_STATUS_NEEDED 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.305: Finger on sensor callback 282s (process:2021): libfprint-device-DEBUG: 17:02:39.305: Device reported finger status change: FP_FINGER_STATUS_PRESENT 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.305: [egismoc] ENROLL_STATES entering state 11 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.305: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.305: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.305: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.305: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.306: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.306: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.306: Read capture callback 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.306: Response prefix valid: yes 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.306: Response suffix valid: yes 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.306: Partial capture successful. Please touch the sensor again (5/10) 282s (process:2021): libfprint-device-DEBUG: 17:02:39.306: Device reported enroll progress, reported 5 of 10 have been completed 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.306: [egismoc] ENROLL_STATES entering state 8 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.306: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.306: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.306: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.306: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.307: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.307: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.307: Task SSM next state callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.307: [egismoc] ENROLL_STATES entering state 9 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.307: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.307: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.307: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.307: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.308: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.308: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.308: Task SSM next state callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.308: [egismoc] ENROLL_STATES entering state 10 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.308: Wait for finger on sensor 282s (process:2021): libfprint-device-DEBUG: 17:02:39.308: Device reported finger status change: FP_FINGER_STATUS_NEEDED 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.308: Finger on sensor callback 282s (process:2021): libfprint-device-DEBUG: 17:02:39.308: Device reported finger status change: FP_FINGER_STATUS_PRESENT 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.308: [egismoc] ENROLL_STATES entering state 11 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.308: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.308: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.308: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.309: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.310: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.310: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.310: Read capture callback 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.310: Response prefix valid: yes 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.310: Response suffix valid: yes 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.310: Partial capture successful. Please touch the sensor again (6/10) 282s (process:2021): libfprint-device-DEBUG: 17:02:39.310: Device reported enroll progress, reported 6 of 10 have been completed 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.310: [egismoc] ENROLL_STATES entering state 8 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.310: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.310: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.310: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.310: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.311: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.311: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.311: Task SSM next state callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.311: [egismoc] ENROLL_STATES entering state 9 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.311: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.311: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.311: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.311: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.312: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.312: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.312: Task SSM next state callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.312: [egismoc] ENROLL_STATES entering state 10 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.312: Wait for finger on sensor 282s (process:2021): libfprint-device-DEBUG: 17:02:39.312: Device reported finger status change: FP_FINGER_STATUS_NEEDED 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.312: Finger on sensor callback 282s (process:2021): libfprint-device-DEBUG: 17:02:39.312: Device reported finger status change: FP_FINGER_STATUS_PRESENT 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.312: [egismoc] ENROLL_STATES entering state 11 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.312: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.312: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.312: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.313: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.313: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.313: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.313: Read capture callback 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.313: Response prefix valid: yes 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.313: Response suffix valid: yes 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.313: Partial capture successful. Please touch the sensor again (7/10) 282s (process:2021): libfprint-device-DEBUG: 17:02:39.313: Device reported enroll progress, reported 7 of 10 have been completed 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.313: [egismoc] ENROLL_STATES entering state 8 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.313: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.313: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.313: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.314: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.314: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.314: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.314: Task SSM next state callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.314: [egismoc] ENROLL_STATES entering state 9 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.314: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.314: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.314: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.314: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.315: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.315: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.315: Task SSM next state callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.315: [egismoc] ENROLL_STATES entering state 10 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.315: Wait for finger on sensor 282s (process:2021): libfprint-device-DEBUG: 17:02:39.315: Device reported finger status change: FP_FINGER_STATUS_NEEDED 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.315: Finger on sensor callback 282s (process:2021): libfprint-device-DEBUG: 17:02:39.315: Device reported finger status change: FP_FINGER_STATUS_PRESENT 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.315: [egismoc] ENROLL_STATES entering state 11 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.315: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.315: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.315: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.316: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.316: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.316: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.316: Read capture callback 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.316: Response prefix valid: yes 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.316: Response suffix valid: yes 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.316: Partial capture successful. Please touch the sensor again (8/10) 282s (process:2021): libfprint-device-DEBUG: 17:02:39.316: Device reported enroll progress, reported 8 of 10 have been completed 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.316: [egismoc] ENROLL_STATES entering state 8 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.316: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.316: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.316: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.317: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.317: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.317: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.317: Task SSM next state callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.317: [egismoc] ENROLL_STATES entering state 9 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.317: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.317: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.317: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.318: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.318: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.318: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.318: Task SSM next state callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.318: [egismoc] ENROLL_STATES entering state 10 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.318: Wait for finger on sensor 282s (process:2021): libfprint-device-DEBUG: 17:02:39.318: Device reported finger status change: FP_FINGER_STATUS_NEEDED 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.319: Finger on sensor callback 282s (process:2021): libfprint-device-DEBUG: 17:02:39.319: Device reported finger status change: FP_FINGER_STATUS_PRESENT 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.319: [egismoc] ENROLL_STATES entering state 11 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.319: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.319: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.319: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.319: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.320: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.320: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.320: Read capture callback 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.320: Response prefix valid: yes 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.320: Response suffix valid: yes 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.320: Partial capture successful. Please touch the sensor again (9/10) 282s (process:2021): libfprint-device-DEBUG: 17:02:39.320: Device reported enroll progress, reported 9 of 10 have been completed 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.320: [egismoc] ENROLL_STATES entering state 8 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.320: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.320: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.320: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.320: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.320: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.321: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.321: Task SSM next state callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.321: [egismoc] ENROLL_STATES entering state 9 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.321: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.321: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.321: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.321: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.321: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.321: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.321: Task SSM next state callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.321: [egismoc] ENROLL_STATES entering state 10 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.321: Wait for finger on sensor 282s (process:2021): libfprint-device-DEBUG: 17:02:39.321: Device reported finger status change: FP_FINGER_STATUS_NEEDED 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.322: Finger on sensor callback 282s (process:2021): libfprint-device-DEBUG: 17:02:39.322: Device reported finger status change: FP_FINGER_STATUS_PRESENT 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.322: [egismoc] ENROLL_STATES entering state 11 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.322: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.322: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.322: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.322: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.323: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.323: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.323: Read capture callback 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.323: Response prefix valid: yes 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.323: Response suffix valid: NO 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.323: Response prefix valid: yes 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.323: Response suffix valid: yes 282s (process:2021): libfprint-device-DEBUG: 17:02:39.323: Device reported enroll progress, reported 9 of 10 have been completed 282s listing - device should have prints 282s clear device storage 282s clear done 282s listing - device should be empty 282s enrolling 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 1, , None, None) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 2, , None, None) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 3, , None, None) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 4, , None, None) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 4, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 5, , None, None) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 6, , None, None) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 7, , None, None) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 8, , None, None) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 9, , None, None) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 10, , None, None) 282s enroll done 282s listing - device should have 1 print 282s verifying 282s verify done 282s async identifying 282s indentification_done: 282s try to enroll duplicate 282s duplicate enroll attempt done 282s listing - device should still only have 1 print 282s enroll new finger 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 1, , None, None) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 1, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 2, , None, None) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 3, , None, None) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 4, , None, None) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 5, , None, None) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 6, , None, None) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 7, , None, None) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 8, , None, None) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 9, , None, None) 282s finger status: 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.323: [egismoc] ENROLL_STATES entering state 8 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.323: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.323: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.323: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.323: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.324: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.324: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.324: Task SSM next state callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.324: [egismoc] ENROLL_STATES entering state 9 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.324: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.324: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.324: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.324: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.325: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.325: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.325: Task SSM next state callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.325: [egismoc] ENROLL_STATES entering state 10 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.325: Wait for finger on sensor 282s (process:2021): libfprint-device-DEBUG: 17:02:39.325: Device reported finger status change: FP_FINGER_STATUS_NEEDED 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.325: Finger on sensor callback 282s (process:2021): libfprint-device-DEBUG: 17:02:39.325: Device reported finger status change: FP_FINGER_STATUS_PRESENT 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.325: [egismoc] ENROLL_STATES entering state 11 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.325: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.325: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.325: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.326: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.326: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.326: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.326: Read capture callback 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.326: Response prefix valid: yes 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.326: Response suffix valid: NO 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.326: Response prefix valid: yes 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.326: Response suffix valid: yes 282s (process:2021): libfprint-device-DEBUG: 17:02:39.326: Device reported enroll progress, reported 9 of 10 have been completed 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.326: [egismoc] ENROLL_STATES entering state 8 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.326: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.326: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.326: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.326: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.327: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.327: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.327: Task SSM next state callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.327: [egismoc] ENROLL_STATES entering state 9 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.327: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.327: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.327: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.327: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.328: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.328: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.328: Task SSM next state callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.328: [egismoc] ENROLL_STATES entering state 10 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.328: Wait for finger on sensor 282s (process:2021): libfprint-device-DEBUG: 17:02:39.328: Device reported finger status change: FP_FINGER_STATUS_NEEDED 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.328: Finger on sensor callback 282s (process:2021): libfprint-device-DEBUG: 17:02:39.328: Device reported finger status change: FP_FINGER_STATUS_PRESENT 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.328: [egismoc] ENROLL_STATES entering state 11 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.328: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.328: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.328: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.329: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.329: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.329: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.329: Read capture callback 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.329: Response prefix valid: yes 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.329: Response suffix valid: NO 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.329: Response prefix valid: yes 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.329: Response suffix valid: yes 282s (process:2021): libfprint-device-DEBUG: 17:02:39.329: Device reported enroll progress, reported 9 of 10 have been completed 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.329: [egismoc] ENROLL_STATES entering state 8 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.329: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.329: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.329: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.330: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.330: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.330: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.330: Task SSM next state callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.330: [egismoc] ENROLL_STATES entering state 9 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.330: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.330: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.330: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.331: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.331: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.331: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.331: Task SSM next state callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.331: [egismoc] ENROLL_STATES entering state 10 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.331: Wait for finger on sensor 282s (process:2021): libfprint-device-DEBUG: 17:02:39.331: Device reported finger status change: FP_FINGER_STATUS_NEEDED 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.331: Finger on sensor callback 282s (process:2021): libfprint-device-DEBUG: 17:02:39.331: Device reported finger status change: FP_FINGER_STATUS_PRESENT 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.331: [egismoc] ENROLL_STATES entering state 11 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.331: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.331: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.331: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.332: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.332: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.332: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.332: Read capture callback 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.332: Response prefix valid: yes 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.332: Response suffix valid: yes 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.332: Partial capture successful. Please touch the sensor again (10/10) 282s (process:2021): libfprint-device-DEBUG: 17:02:39.332: Device reported enroll progress, reported 10 of 10 have been completed 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.332: [egismoc] ENROLL_STATES entering state 12 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.332: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.332: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.332: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.333: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.333: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.333: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.333: Task SSM next state callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.333: [egismoc] ENROLL_STATES entering state 13 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.333: New fingerprint ID: FP1-00000000-7-00000000-nobody 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.333: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.333: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.333: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.334: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.334: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.334: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.334: Task SSM next state callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.334: [egismoc] ENROLL_STATES entering state 14 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.334: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.334: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.334: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.335: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.335: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.335: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.335: Task SSM next state callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.335: [egismoc] ENROLL_STATES entering state 15 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.335: Enrollment was successful! 282s (process:2021): libfprint-device-DEBUG: 17:02:39.335: Device reported enroll completion 282s (process:2021): libfprint-device-DEBUG: 17:02:39.335: Device reported finger status change: FP_FINGER_STATUS_NONE 282s (process:2021): libfprint-device-DEBUG: 17:02:39.335: Print for finger FP_FINGER_RIGHT_INDEX enrolled 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.335: [egismoc] ENROLL_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.335: Task SSM done 282s (process:2021): libfprint-device-DEBUG: 17:02:39.335: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 282s (process:2021): libfprint-device-DEBUG: 17:02:39.335: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.335: List 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.335: [egismoc] LIST_STATES entering state 0 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.335: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.335: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.335: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.336: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.336: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.336: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.336: List callback 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.336: Device fingerprint 0: FP1-00000000-2-00000000-nobody 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.336: Device fingerprint 1: FP1-00000000-7-00000000-nobody 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.336: Number of currently enrolled fingerprints on the device is 2 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.336: [egismoc] LIST_STATES entering state 1 282s (process:2021): libfprint-device-DEBUG: 17:02:39.336: Device reported listing completion 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.336: [egismoc] LIST_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.336: Task SSM done 282s (process:2021): libfprint-device-DEBUG: 17:02:39.336: Completing action FPI_DEVICE_ACTION_LIST in idle! 282s (process:2021): libfprint-device-DEBUG: 17:02:39.336: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.336: Delete 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.336: [egismoc] DELETE_STATES entering state 0 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.336: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.336: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.336: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.337: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.337: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.337: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.337: List callback 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.337: Device fingerprint 0: FP1-00000000-2-00000000-nobody 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.337: Device fingerprint 1: FP1-00000000-7-00000000-nobody 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.337: Number of currently enrolled fingerprints on the device is 2 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.337: [egismoc] DELETE_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.337: Get delete command 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.337: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.337: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.337: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.337: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.338: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.338: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.338: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.338: Delete callback 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.338: Response prefix valid: yes 282s (process:2021): libfprint-device-DEBUG: 17:02:39.338: Device reported deletion completion 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.338: [egismoc] DELETE_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.338: Task SSM done 282s (process:2021): libfprint-device-DEBUG: 17:02:39.338: Completing action FPI_DEVICE_ACTION_DELETE in idle! 282s (process:2021): libfprint-device-DEBUG: 17:02:39.338: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.338: List 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.338: [egismoc] LIST_STATES entering state 0 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.338: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.338: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.338: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.338: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.339: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.339: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.339: List callback 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.339: Device fingerprint 0: FP1-00000000-7-00000000-nobody 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.339: Number of currently enrolled fingerprints on the device is 1 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.339: [egismoc] LIST_STATES entering state 1 282s (process:2021): libfprint-device-DEBUG: 17:02:39.339: Device reported listing completion 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.339: [egismoc] LIST_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.339: Task SSM done 282s (process:2021): libfprint-device-DEBUG: 17:02:39.339: Completing action FPI_DEVICE_ACTION_LIST in idle! 282s (process:2021): libfprint-device-DEBUG: 17:02:39.339: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.339: Clear storage 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.339: [egismoc] DELETE_STATES entering state 0 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.339: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.339: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.339: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.340: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.340: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.340: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.340: List callback 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.340: Device fingerprint 0: FP1-00000000-7-00000000-nobody 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.340: Number of currently enrolled fingerprints on the device is 1 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.340: [egismoc] DELETE_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.340: Get delete command 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.340: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.340: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.340: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.340: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.341: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.341: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.341: Delete callback 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.341: Response prefix valid: yes 282s (process:2021): libfprint-device-DEBUG: 17:02:39.341: Device reported deletion completion 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.341: [egismoc] DELETE_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.341: Task SSM done 282s (process:2021): libfprint-device-DEBUG: 17:02:39.341: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 282s (process:2021): libfprint-device-DEBUG: 17:02:39.341: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.341: List 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.341: [egismoc] LIST_STATES entering state 0 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.341: Execute command and get response 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.341: Get check bytes 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.341: [egismoc] CMD_STATES entering state 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.341: [egismoc] CMD_STATES entering state 1 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.342: Command receive callback 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.342: [egismoc] CMD_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.342: List callback 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.342: Number of currently enrolled fingerprints on the device is 0 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.342: [egismoc] LIST_STATES entering state 1 282s (process:2021): libfprint-device-DEBUG: 17:02:39.342: Device reported listing completion 282s (process:2021): libfprint-SSM-DEBUG: 17:02:39.342: [egismoc] LIST_STATES completed successfully 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.342: Task SSM done 282s (process:2021): libfprint-device-DEBUG: 17:02:39.342: Completing action FPI_DEVICE_ACTION_LIST in idle! 282s (process:2021): libfprint-device-DEBUG: 17:02:39.342: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.342: Closing device 282s (process:2021): libfprint-egismoc-DEBUG: 17:02:39.342: Cancel 282s (process:2021): libfprint-device-DEBUG: 17:02:39.342: Device reported close completion 282s (process:2021): libfprint-device-DEBUG: 17:02:39.342: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 282s (process:2021): libfprint-device-DEBUG: 17:02:39.342: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 282s finger status: 282s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xfe6ebf90a100 (FpiDeviceEgisMoc at 0x344c50f0)>, 10, , None, None) 282s enroll new finger done 282s listing - device should have 2 prints 282s deleting first print 282s delete done 282s listing - device should only have second print 282s clear device storage 282s clear done 282s listing - device should be empty 282s ** (umockdev-run:2017): DEBUG: 17:02:39.355: umockdev.vala:150: Removing test bed /tmp/umockdev.E8ZAK2 282s (umockdev-run:2017): GLib-DEBUG: 17:02:39.358: unsetenv() is not thread-safe and should not be used after threads are created 282s PASS: libfprint-2/driver-egismoc.test 282s Running test: libfprint-2/driver-elan-cobo.test 282s ** (umockdev-run:2029): DEBUG: 17:02:39.400: umockdev.vala:123: Created udev test bed /tmp/umockdev.B0NEK2 282s ** (umockdev-run:2029): DEBUG: 17:02:39.401: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 282s ** (umockdev-run:2029): DEBUG: 17:02:39.402: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 282s ** (umockdev-run:2029): DEBUG: 17:02:39.404: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.B0NEK2/dev/bus/usb/001/045 282s ** (umockdev-run:2029): DEBUG: 17:02:39.404: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 282s ** (umockdev-run:2029): DEBUG: 17:02:39.404: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 282s ** (umockdev-run:2029): DEBUG: 17:02:39.406: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.B0NEK2/dev/bus/usb/001/001 282s ** (umockdev-run:2029): DEBUG: 17:02:39.406: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 282s ** (umockdev-run:2029): DEBUG: 17:02:39.407: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 282s (process:2033): libfprint-context-DEBUG: 17:02:39.454: Initializing FpContext (libfprint version 1.94.7+tod1) 282s (process:2033): libfprint-tod-DEBUG: 17:02:39.455: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 282s (process:2033): libfprint-context-DEBUG: 17:02:39.456: No driver found for USB device 1D6B:0002 282s (process:2033): libfprint-device-DEBUG: 17:02:39.457: Device reported probe completion 282s (process:2033): libfprint-device-DEBUG: 17:02:39.457: Completing action FPI_DEVICE_ACTION_PROBE in idle! 282s (process:2033): libfprint-device-DEBUG: 17:02:39.457: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle fo(process:2033): libfprint-elan-DEBUG: 17:02:39.459: 115444316: ../libfprint/drivers/elan.c:908 282s (process:2033): libfprint-image_device-DEBUG: 17:02:39.459: Image device open completed 282s (process:2033): libfprint-device-DEBUG: 17:02:39.459: Device reported open completion 282s (process:2033): libfprint-device-DEBUG: 17:02:39.459: Completing action FPI_DEVICE_ACTION_OPEN in idle! 282s (process:2033): libfprint-device-DEBUG: 17:02:39.459: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 282s (process:2033): libfprint-device-DEBUG: 17:02:39.459: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 282s (process:2033): libfprint-image_device-DEBUG: 17:02:39.459: Activating image device 282s (process:2033): libfprint-image_device-DEBUG: 17:02:39.459: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.460: 115444930: ../libfprint/drivers/elan.c:960 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.460: 115444961: ../libfprint/drivers/elan.c:951 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.460: 115444991: ../libfprint/drivers/elan.c:892 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.460: 115445020: ../libfprint/drivers/elan.c:100 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.460: [elan] ACTIVATE_NUM_STATES entering state 0 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.460: 115445084: ../libfprint/drivers/elan.c:820 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.460: 115445529: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.460: 115445568: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.460: 115445595: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.461: 115446071: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.461: 115446116: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.461: [elan] ACTIVATE_NUM_STATES entering state 1 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.461: 115446216: ../libfprint/drivers/elan.c:820 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.461: FW ver 0x0140 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.461: [elan] ACTIVATE_NUM_STATES entering state 2 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.461: 115446301: ../libfprint/drivers/elan.c:820 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.461: 115446693: ../libfprint/drivers/elan.c:346 282s r fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s libusb: error [op_handle_events] cannot find handle for fd 9 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.461: 115446728: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.461: 115446762: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.462: 115447223: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.462: 115447259: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.462: [elan] ACTIVATE_NUM_STATES entering state 3 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.462: 115447349: ../libfprint/drivers/elan.c:820 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.462: sensor dimensions, WxH: 144x64 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.462: [elan] ACTIVATE_NUM_STATES entering state 4 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.462: 115447481: ../libfprint/drivers/elan.c:820 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.462: skipping command 0x40 0x2a for this device (for devices 0x1 but device is 0x0) 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.462: 115447632: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.462: [elan] ACTIVATE_NUM_STATES completed successfully 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.462: 115447772: ../libfprint/drivers/elan.c:881 282s (process:2033): libfprint-image_device-DEBUG: 17:02:39.462: Image device activation completed 282s (process:2033): libfprint-image_device-DEBUG: 17:02:39.463: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.463: 115448282: ../libfprint/drivers/elan.c:960 282s (process:2033): libfprint-image_device-DEBUG: 17:02:39.463: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.463: 115448433: ../libfprint/drivers/elan.c:960 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.463: 115448544: ../libfprint/drivers/elan.c:792 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.463: 115448573: ../libfprint/drivers/elan.c:100 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.463: [elan] CALIBRATE_NUM_STATES entering state 0 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.463: 115448709: ../libfprint/drivers/elan.c:691 282s (process:2033): libfprint-device-DEBUG: 17:02:39.464: Device reported finger status change: FP_FINGER_STATUS_NEEDED 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.464: 115449208: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.464: 115449217: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.464: 115449220: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.464: 115449691: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.464: 115449715: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.464: [elan] CALIBRATE_NUM_STATES entering state 1 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.464: 115449722: ../libfprint/drivers/elan.c:691 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.464: 115449725: ../libfprint/drivers/elan.c:156 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.464: 115449728: ../libfprint/drivers/elan.c:118 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.464: [elan] CALIBRATE_NUM_STATES entering state 2 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.464: 115449743: ../libfprint/drivers/elan.c:691 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.465: 115450190: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.465: 115450199: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.465: 115450202: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.465: 115450642: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.465: 115450651: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.465: [elan] CALIBRATE_NUM_STATES entering state 3 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.465: 115450657: ../libfprint/drivers/elan.c:691 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.465: 115450660: ../libfprint/drivers/elan.c:634 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.465: calibration mean: 8248, bg mean: 7978, delta: 270 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.465: [elan] CALIBRATE_NUM_STATES completed successfully 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.465: 115450674: ../libfprint/drivers/elan.c:776 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.465: 115450677: ../libfprint/drivers/elan.c:620 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.465: 115450679: ../libfprint/drivers/elan.c:100 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.465: [elan] CAPTURE_NUM_STATES entering state 0 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.466: 115451102: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.466: 115451112: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.466: 115451115: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.466: skipping read, not expecting anything 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.466: 115451120: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.466: [elan] CAPTURE_NUM_STATES entering state 1 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.466: 115451534: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.466: 115451543: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.466: 115451546: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.467: 115452025: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.467: 115452036: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.467: [elan] CAPTURE_NUM_STATES entering state 2 282s (process:2033): libfprint-device-DEBUG: 17:02:39.467: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 282s (process:2033): libfprint-image_device-DEBUG: 17:02:39.467: Image device reported finger status: on 282s (process:2033): libfprint-image_device-DEBUG: 17:02:39.467: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.467: 115452058: ../libfprint/drivers/elan.c:960 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.467: 115452502: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.467: 115452512: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.467: 115452515: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.468: 115452969: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.468: 115452992: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.468: [elan] CAPTURE_NUM_STATES entering state 3 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.468: 115452999: ../libfprint/drivers/elan.c:203 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.468: 115453002: ../libfprint/drivers/elan.c:118 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.468: [elan] CAPTURE_NUM_STATES entering state 1 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.468: 115453466: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.468: 115453506: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.468: 115453513: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.469: 115453933: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.469: 115453942: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.469: [elan] CAPTURE_NUM_STATES entering state 2 282s (process:2033): libfprint-image_device-DEBUG: 17:02:39.469: Image device reported finger status: on 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.469: 115454380: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.469: 115454390: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.469: 115454393: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.469: 115454859: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.469: 115454870: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.469: [elan] CAPTURE_NUM_STATES entering state 3 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.469: 115454877: ../libfprint/drivers/elan.c:203 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.469: 115454884: ../libfprint/drivers/elan.c:118 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.470: [elan] CAPTURE_NUM_STATES entering state 1 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.470: 115455253: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.470: 115455262: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.470: 115455265: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.470: 115455736: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.470: 115455771: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.470: [elan] CAPTURE_NUM_STATES entering state 2 282s (process:2033): libfprint-image_device-DEBUG: 17:02:39.470: Image device reported finger status: on 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.471: 115456201: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.471: 115456210: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.471: 115456213: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.471: 115456702: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.471: 115456713: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.471: [elan] CAPTURE_NUM_STATES entering state 3 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.471: 115456720: ../libfprint/drivers/elan.c:203 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.471: 115456728: ../libfprint/drivers/elan.c:118 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.471: [elan] CAPTURE_NUM_STATES entering state 1 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.472: 115457183: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.472: 115457192: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.472: 115457195: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.472: 115457623: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.472: 115457631: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.472: [elan] CAPTURE_NUM_STATES entering state 2 282s (process:2033): libfprint-image_device-DEBUG: 17:02:39.472: Image device reported finger status: on 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.473: 115458018: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.473: 115458026: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.473: 115458029: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.473: 115458493: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.473: 115458504: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.473: [elan] CAPTURE_NUM_STATES entering state 3 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.473: 115458511: ../libfprint/drivers/elan.c:203 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.473: 115458518: ../libfprint/drivers/elan.c:118 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.473: [elan] CAPTURE_NUM_STATES entering state 1 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.474: 115458972: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.474: 115459014: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.474: 115459049: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.474: 115459455: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.474: 115459464: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.474: [elan] CAPTURE_NUM_STATES entering state 2 282s (process:2033): libfprint-image_device-DEBUG: 17:02:39.474: Image device reported finger status: on 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.474: 115459896: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.474: 115459905: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.475: 115459908: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.475: 115460448: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.475: 115460460: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.475: [elan] CAPTURE_NUM_STATES entering state 3 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.475: 115460467: ../libfprint/drivers/elan.c:203 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.475: 115460475: ../libfprint/drivers/elan.c:118 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.475: [elan] CAPTURE_NUM_STATES entering state 1 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.475: 115460855: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.475: 115460863: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.475: 115460866: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.476: 115461331: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.476: 115461364: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.476: [elan] CAPTURE_NUM_STATES entering state 2 282s (process:2033): libfprint-image_device-DEBUG: 17:02:39.476: Image device reported finger status: on 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.476: 115461794: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.476: 115461803: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.476: 115461805: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.477: 115462263: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.477: 115462275: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.477: [elan] CAPTURE_NUM_STATES entering state 3 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.477: 115462281: ../libfprint/drivers/elan.c:203 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.477: 115462289: ../libfprint/drivers/elan.c:118 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.477: [elan] CAPTURE_NUM_STATES entering state 1 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.477: 115462755: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.477: 115462783: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.477: 115462790: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.478: 115463216: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.478: 115463225: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.478: [elan] CAPTURE_NUM_STATES entering state 2 282s (process:2033): libfprint-image_device-DEBUG: 17:02:39.478: Image device reported finger status: on 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.478: 115463714: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.478: 115463776: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.478: 115463783: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.479: 115464284: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.479: 115464311: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.479: [elan] CAPTURE_NUM_STATES entering state 3 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.479: 115464322: ../libfprint/drivers/elan.c:203 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.479: 115464329: ../libfprint/drivers/elan.c:118 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.479: [elan] CAPTURE_NUM_STATES entering state 1 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.479: 115464681: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.479: 115464689: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.479: 115464693: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.480: 115465153: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.480: 115465218: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.480: [elan] CAPTURE_NUM_STATES entering state 2 282s (process:2033): libfprint-image_device-DEBUG: 17:02:39.480: Image device reported finger status: on 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.480: 115465592: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.480: 115465600: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.480: 115465604: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.481: 115466036: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.481: 115466046: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.481: [elan] CAPTURE_NUM_STATES entering state 3 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.481: 115466053: ../libfprint/drivers/elan.c:203 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.481: 115466060: ../libfprint/drivers/elan.c:118 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.481: [elan] CAPTURE_NUM_STATES entering state 1 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.481: 115466542: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.481: 115466562: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.481: 115466568: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.482: 115467044: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.482: 115467053: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.482: [elan] CAPTURE_NUM_STATES entering state 2 282s (process:2033): libfprint-image_device-DEBUG: 17:02:39.482: Image device reported finger status: on 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.482: 115467494: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.482: 115467503: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.482: 115467506: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.483: 115467992: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.483: 115468021: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.483: [elan] CAPTURE_NUM_STATES entering state 3 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.483: 115468030: ../libfprint/drivers/elan.c:203 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.483: 115468050: ../libfprint/drivers/elan.c:118 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.483: [elan] CAPTURE_NUM_STATES entering state 1 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.483: 115468524: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.483: 115468534: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.483: 115468537: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.484: 115469002: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.484: 115469011: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.484: [elan] CAPTURE_NUM_STATES entering state 2 282s (process:2033): libfprint-image_device-DEBUG: 17:02:39.484: Image device reported finger status: on 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.484: 115469464: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.484: 115469474: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.484: 115469476: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.485: 115469937: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.485: 115469947: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.485: [elan] CAPTURE_NUM_STATES entering state 3 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.485: 115469954: ../libfprint/drivers/elan.c:203 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.485: 115469962: ../libfprint/drivers/elan.c:118 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.485: [elan] CAPTURE_NUM_STATES entering state 1 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.485: 115470425: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.485: 115470435: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.485: 115470437: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.485: 115470774: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.485: 115470798: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.485: [elan] CAPTURE_NUM_STATES entering state 2 282s (process:2033): libfprint-image_device-DEBUG: 17:02:39.485: Image device reported finger status: on 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.486: 115471251: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.486: 115471292: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.486: 115471299: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.486: 115471722: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.486: 115471733: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.486: [elan] CAPTURE_NUM_STATES entering state 3 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.486: 115471739: ../libfprint/drivers/elan.c:203 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.486: 115471747: ../libfprint/drivers/elan.c:118 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.486: [elan] CAPTURE_NUM_STATES entering state 1 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.487: 115472193: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.487: 115472202: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.487: 115472205: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.487: 115472648: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.487: 115472658: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.487: [elan] CAPTURE_NUM_STATES entering state 2 282s (process:2033): libfprint-image_device-DEBUG: 17:02:39.487: Image device reported finger status: on 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.488: 115473044: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.488: 115473053: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.488: 115473056: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.488: 115473486: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.488: 115473497: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.488: [elan] CAPTURE_NUM_STATES entering state 3 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.488: 115473503: ../libfprint/drivers/elan.c:203 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.488: 115473510: ../libfprint/drivers/elan.c:118 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.488: [elan] CAPTURE_NUM_STATES entering state 1 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.489: 115473985: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.489: 115474005: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.489: 115474011: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.489: 115474456: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.489: 115474465: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.489: [elan] CAPTURE_NUM_STATES entering state 2 282s (process:2033): libfprint-image_device-DEBUG: 17:02:39.489: Image device reported finger status: on 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.489: 115474864: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.489: 115474872: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.489: 115474875: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.490: 115475233: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.490: 115475243: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.490: [elan] CAPTURE_NUM_STATES entering state 3 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.490: 115475249: ../libfprint/drivers/elan.c:203 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.490: 115475260: ../libfprint/drivers/elan.c:118 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.490: [elan] CAPTURE_NUM_STATES entering state 1 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.490: 115475723: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.490: 115475742: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.490: 115475794: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.491: 115476245: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.491: 115476277: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.491: [elan] CAPTURE_NUM_STATES entering state 2 282s (process:2033): libfprint-image_device-DEBUG: 17:02:39.491: Image device reported finger status: on 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.491: 115476709: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.491: 115476718: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.491: 115476721: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.492: 115477161: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.492: 115477172: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.492: [elan] CAPTURE_NUM_STATES entering state 3 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.492: 115477179: ../libfprint/drivers/elan.c:203 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.492: 115477186: ../libfprint/drivers/elan.c:118 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.492: [elan] CAPTURE_NUM_STATES entering state 1 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.492: 115477635: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.492: 115477644: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.492: 115477647: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.493: 115477983: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.493: 115478001: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.493: [elan] CAPTURE_NUM_STATES entering state 2 282s (process:2033): libfprint-image_device-DEBUG: 17:02:39.493: Image device reported finger status: on 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.493: 115478358: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.493: 115478368: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.493: 115478371: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.493: 115478741: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.493: 115478752: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.493: [elan] CAPTURE_NUM_STATES entering state 3 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.493: 115478759: ../libfprint/drivers/elan.c:203 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.493: 115478766: ../libfprint/drivers/elan.c:118 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.493: [elan] CAPTURE_NUM_STATES entering state 1 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.494: 115479222: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.494: 115479231: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.494: 115479234: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.494: 115479661: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.494: 115479670: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.494: [elan] CAPTURE_NUM_STATES entering state 2 282s (process:2033): libfprint-image_device-DEBUG: 17:02:39.494: Image device reported finger status: on 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.495: 115480019: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.495: 115480042: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.495: 115480070: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.495: 115480523: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.495: 115480534: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.495: [elan] CAPTURE_NUM_STATES entering state 3 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.495: 115480540: ../libfprint/drivers/elan.c:203 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.495: 115480547: ../libfprint/drivers/elan.c:118 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.495: [elan] CAPTURE_NUM_STATES entering state 1 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.496: 115481037: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.496: 115481047: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.496: 115481050: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.496: 115481465: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.496: 115481474: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.496: [elan] CAPTURE_NUM_STATES entering state 2 282s (process:2033): libfprint-SSM-DEBUG: 17:02:39.496: [elan] CAPTURE_NUM_STATES completed successfully 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.496: 115481488: ../libfprint/drivers/elan.c:586 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.496: 115481490: ../libfprint/drivers/elan.c:315 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.496: 115481495: ../libfprint/drivers/elan.c:272 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.497: 115482225: ../libfprint/drivers/elan.c:272 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.498: 115482948: ../libfprint/drivers/elan.c:272 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.498: 115483661: ../libfprint/drivers/elan.c:272 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.500: 115485102: ../libfprint/drivers/elan.c:272 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.502: 115486956: ../libfprint/drivers/elan.c:272 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.504: 115488921: ../libfprint/drivers/elan.c:272 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.505: 115490887: ../libfprint/drivers/elan.c:272 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.507: 115492824: ../libfprint/drivers/elan.c:272 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.509: 115494750: ../libfprint/drivers/elan.c:272 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.511: 115496772: ../libfprint/drivers/elan.c:272 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.513: 115498877: ../libfprint/drivers/elan.c:272 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.514: 115499671: ../libfprint/drivers/elan.c:272 282s (process:2033): libfprint-elan-DEBUG: 17:02:39.516: 115501619: ../libfprint/drivers/elan.c:272 282s (process:2033): libfprint-assembling-DEBUG: 17:02:39.952: calc delta completed in 0.434732 secs 282s (process:2033): libfprint-assembling-DEBUG: 17:02:40.401: calc delta completed in 0.448915 secs 282s (process:2033): libfprint-assembling-DEBUG: 17:02:40.401: errors: 133465 rev: 143589 282s (process:2033): libfprint-assembling-DEBUG: 17:02:40.843: calc delta completed in 0.441419 secs 282s (process:2033): libfprint-assembling-DEBUG: 17:02:40.843: height is 225 282s (process:2033): libfprint-image_device-DEBUG: 17:02:40.844: Image device captured an image 282s (process:2033): libfprint-image_device-DEBUG: 17:02:40.845: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 282s (process:2033): libfprint-elan-DEBUG: 17:02:40.845: 116830652: ../libfprint/drivers/elan.c:960 282s (process:2033): libfprint-device-DEBUG: 17:02:40.846: Device reported finger status change: FP_FINGER_STATUS_PRESENT 282s (process:2033): libfprint-elan-DEBUG: 17:02:40.846: 116830953: ../libfprint/drivers/elan.c:507 282s (process:2033): libfprint-elan-DEBUG: 17:02:40.846: 116830958: ../libfprint/drivers/elan.c:100 282s (process:2033): libfprint-SSM-DEBUG: 17:02:40.846: [elan] STOP_CAPTURE_NUM_STATES entering state 0 282s (process:2033): libfprint-elan-DEBUG: 17:02:40.846: 116830970: ../libfprint/drivers/elan.c:466 282s (process:2033): libfprint-device-DEBUG: 17:02:40.847: Updated temperature model after 1.39 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 282s (process:2033): libfprint-elan-DEBUG: 17:02:40.847: 116832457: ../libfprint/drivers/elan.c:346 282s (process:2033): libfprint-elan-DEBUG: 17:02:40.847: 116832464: ../libfprint/drivers/elan.c:366 282s (process:2033): libfprint-elan-DEBUG: 17:02:40.847: 116832467: ../libfprint/drivers/elan.c:379 282s (process:2033): libfprint-elan-DEBUG: 17:02:40.847: skipping read, not expecting anything 282s (process:2033): libfprint-elan-DEBUG: 17:02:40.847: 116832472: ../libfprint/drivers/elan.c:335 282s (process:2033): libfprint-SSM-DEBUG: 17:02:40.847: [elan] STOP_CAPTURE_NUM_STATES completed successfully 282s (process:2033): libfprint-elan-DEBUG: 17:02:40.847: 116832479: ../libfprint/drivers/elan.c:483 282s (process:2033): libfprint-device-DEBUG: 17:02:40.847: Device reported finger status change: FP_FINGER_STATUS_NONE 282s (process:2033): libfprint-image_device-DEBUG: 17:02:40.847: Image device reported finger status: off 282s (process:2033): libfprint-image_device-DEBUG: 17:02:40.847: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 282s (process:2033): libfprint-elan-DEBUG: 17:02:40.847: 116832494: ../libfprint/drivers/elan.c:960 282s (process:2033): libfprint-image_device-DEBUG: 17:02:40.847: Deactivating image device 282s (process:2033): libfprint-image_device-DEBUG: 17:02:40.847: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 282s (process:2033): libfprint-elan-DEBUG: 17:02:40.847: 116832512: ../libfprint/drivers/elan.c:960 282s (process:2033): libfprint-elan-DEBUG: 17:02:40.847: 116832515: ../libfprint/drivers/elan.c:975 282s (process:2033): libfprint-image_device-DEBUG: 17:02:40.847: Image device deactivation completed 282s (process:2033): libfprint-image_device-DEBUG: 17:02:40.847: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 282s (process:2033): libfprint-elan-DEBUG: 17:02:40.847: 116832526: ../libfprint/drivers/elan.c:960 282s (process:2033): libfprint-image-DEBUG: 17:02:40.882: Minutiae scan completed in 0.035815 secs 282s (process:2033): libfprint-device-DEBUG: 17:02:40.882: Device reported capture completion 282s (process:2033): libfprint-device-DEBUG: 17:02:40.882: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 282s (process:2033): libfprint-device-DEBUG: 17:02:40.882: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 282s (process:2033): libfprint-elan-DEBUG: 17:02:40.883: 116868026: ../libfprint/drivers/elan.c:939 282s (process:2033): libfprint-elan-DEBUG: 17:02:40.883: 116868037: ../libfprint/drivers/elan.c:100 282s (process:2033): libfprint-image_device-DEBUG: 17:02:40.883: Image device close completed 282s (process:2033): libfprint-device-DEBUG: 17:02:40.883: Device reported close completion 282s (process:2033): libfprint-device-DEBUG: 17:02:40.883: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 282s (process:2033): libfprint-device-DEBUG: 17:02:40.883: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 282s ** (umockdev-run:2029): DEBUG: 17:02:40.962: umockdev.vala:150: Removing test bed /tmp/umockdev.B0NEK2 282s (umockdev-run:2029): GLib-DEBUG: 17:02:40.965: unsetenv() is not thread-safe and should not be used after threads are created 283s Comparing PNGs /tmp/libfprint-umockdev-test-7j30hb01/capture.png and /usr/share/installed-tests/libfprint-2/elan-cobo/capture.png 283s PASS: libfprint-2/driver-elan-cobo.test 283s Running test: libfprint-2/driver-elanspi.test 283s Executing: libfprint-2/driver-elanspi.test 283s ** (umockdev-run:2042): DEBUG: 17:02:41.028: umockdev.vala:123: Created udev test bed /tmp/umockdev.FSLBK2 283s ** (umockdev-run:2042): DEBUG: 17:02:41.029: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00/0018:04F3:3057.0001/hidraw/hidraw0 283s ** (umockdev-run:2042): DEBUG: 17:02:41.029: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00/0018:04F3:3057.0001/hidraw/hidraw0 (subsystem hidraw) 283s ** (umockdev-run:2042): DEBUG: 17:02:41.030: umockdev.vala:1430: create_node_for_device: creating pty device /tmp/umockdev.FSLBK2/dev/hidraw0: got pty /dev/pts/0 283s ** (umockdev-run:2042): DEBUG: 17:02:41.030: umockdev.vala:1451: create_node_for_device: creating ptymap symlink /tmp/umockdev.FSLBK2/dev/.ptymap/_dev_pts_0 283s ** (umockdev-run:2042): DEBUG: 17:02:41.030: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00/0018:04F3:3057.0001 283s ** (umockdev-run:2042): DEBUG: 17:02:41.030: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00/0018:04F3:3057.0001 (subsystem hid) 283s ** (umockdev-run:2042): DEBUG: 17:02:41.031: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00 283s ** (umockdev-run:2042): DEBUG: 17:02:41.031: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00 (subsystem i2c) 283s ** (umockdev-run:2042): DEBUG: 17:02:41.032: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1 283s ** (umockdev-run:2042): DEBUG: 17:02:41.032: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1 (subsystem i2c) 283s ** (umockdev-run:2042): DEBUG: 17:02:41.033: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1 283s ** (umockdev-run:2042): DEBUG: 17:02:41.033: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1 (subsystem platform) 283s ** (umockdev-run:2042): DEBUG: 17:02:41.033: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:15.1 283s ** (umockdev-run:2042): DEBUG: 17:02:41.033: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:15.1 (subsystem pci) 283s ** (umockdev-run:2042): DEBUG: 17:02:41.035: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00/spidev/spidev0.0 283s ** (umockdev-run:2042): DEBUG: 17:02:41.035: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00/spidev/spidev0.0 (subsystem spidev) 283s ** (umockdev-run:2042): DEBUG: 17:02:41.036: umockdev.vala:1430: create_node_for_device: creating pty device /tmp/umockdev.FSLBK2/dev/spidev0.0: got pty /dev/pts/1 283s ** (umockdev-run:2042): DEBUG: 17:02:41.036: umockdev.vala:1451: create_node_for_device: creating ptymap symlink /tmp/umockdev.FSLBK2/dev/.ptymap/_dev_pts_1 283s ** (umockdev-run:2042): DEBUG: 17:02:41.036: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00 283s ** (umockdev-run:2042): DEBUG: 17:02:41.036: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00 (subsystem spi) 283s ** (umockdev-run:2042): DEBUG: 17:02:41.038: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0 283s ** (umockdev-run:2042): DEBUG: 17:02:41.038: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0 (subsystem spi_master) 283s ** (umockdev-run:2042): DEBUG: 17:02:41.040: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3 283s ** (umockdev-run:2042): DEBUG: 17:02:41.040: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3 (subsystem platform) 283s ** (umockdev-run:2042): DEBUG: 17:02:41.040: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1e.2 283s ** (umockdev-run:2042): DEBUG: 17:02:41.041: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1e.2 (subsystem pci) 283s (umockdev-run:2042): GLib-GIO-DEBUG: 17:02:41.042: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 283s (process:2046): libfprint-context-DEBUG: 17:02:41.116: Initializing FpContext (libfprint version 1.94.7+tod1) 283s (process:2046): libfprint-tod-DEBUG: 17:02:41.117: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 283s (process:2046): libfprint-device-DEBUG: 17:02:41.119: Device reported probe completion 283s (process:2046): libfprint-device-DEBUG: 17:02:41.119: Completing action FPI_DEVICE_ACTION_PROBE in idle! 283s (process:2046): libfprint-device-DEBUG: 17:02:41.119: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.120: 117105058: ../libfprint/drivers/elanspi.c:1562 283s (process:2046): libfprint-image_device-DEBUG: 17:02:41.120: Image device open completed 283s (process:2046): libfprint-device-DEBUG: 17:02:41.120: Device reported open completion 283s (process:2046): libfprint-device-DEBUG: 17:02:41.120: Completing action FPI_DEVICE_ACTION_OPEN in idle! 283s (process:2046): libfprint-device-DEBUG: 17:02:41.120: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 283s (process:2046): libfprint-device-DEBUG: 17:02:41.120: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 283s (process:2046): libfprint-image_device-DEBUG: 17:02:41.120: Activating image device 283s (process:2046): libfprint-image_device-DEBUG: 17:02:41.120: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.121: [elanspi] ELANSPI_INIT_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.121: [elanspi] ELANSPI_INIT_NSTATES entering state 1 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.121: got status 81 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.121: sync hw reset 283s libfprint-Message: 17:02:41.121: Failed to read spidev block size, using 4096 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.121: [elanspi] ELANSPI_INIT_NSTATES entering state 2 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.125: [elanspi] ELANSPI_INIT_NSTATES entering state 3 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.125: sw reset ok 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.126: [elanspi] ELANSPI_INIT_NSTATES entering state 4 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.126: raw height = 96 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.126: [elanspi] ELANSPI_INIT_NSTATES entering state 5 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.126: raw width = 96 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.126: [elanspi] ELANSPI_INIT_NSTATES entering state 6 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.126: raw reg17 = 175 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.127: [elanspi] ELANSPI_INIT_NSTATES entering state 7 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.127: raw version = 09 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.127: after hardcoded lookup; 96x96, version 1 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.127: found sensor ID 6 => [eFSA96SA] (96 x 96) 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.127: [elanspi] ELANSPI_INIT_NSTATES entering state 8 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.131: [elanspi] ELANSPI_INIT_NSTATES entering state 9 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.131: [elanspi] ELANSPI_INIT_NSTATES entering state 10 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.132: [elanspi] ELANSPI_INIT_NSTATES entering state 11 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.132: [elanspi] ELANSPI_INIT_NSTATES entering state 12 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.132: [elanspi] ELANSPI_INIT_NSTATES entering state 13 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.132: [elanspi] ELANSPI_INIT_NSTATES entering state 14 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.132: [elanspi] ELANSPI_INIT_NSTATES entering state 17 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.132: got vcm mode = 2 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.133: [elanspi] ELANSPI_INIT_NSTATES entering state 18 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.133: [elanspi] ELANSPI_INIT_NSTATES entering state 19 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.133: starting calibrate 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.133: [elanspi] old calibrate entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.134: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.134: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.134: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.135: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.135: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.135: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.135: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.135: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.135: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.135: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.135: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.136: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.136: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.136: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.136: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.136: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.136: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.136: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.136: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.137: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.137: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.137: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.137: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.137: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.137: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.137: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.137: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.137: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.138: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.138: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.138: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.138: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.138: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.138: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.138: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.138: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.138: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.139: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.139: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.139: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.139: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.139: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.139: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.139: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.139: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.139: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.139: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.140: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.140: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.140: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.140: [elanspi] ELANSPI_WRTABLE_NSTATES completed successfully 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.140: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.177: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.177: dac init is 0x29 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.178: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.215: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.215: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 283s (process:2046): libfprint-device-DEBUG: 17:02:41.220: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.259: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.259: calibration ok, saving bg image 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.259: [elanspi] old calibrate completed successfully 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.259: [elanspi] ELANSPI_INIT_NSTATES entering state 20 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.259: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.301: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.301: [elanspi] ELANSPI_INIT_NSTATES entering state 21 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.301: [elanspi] ELANSPI_INIT_NSTATES completed successfully 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.301: 117286195: ../libfprint/drivers/elanspi.c:1596 283s (process:2046): libfprint-image_device-DEBUG: 17:02:41.301: Image device activation completed 283s (process:2046): libfprint-image_device-DEBUG: 17:02:41.301: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 283s (process:2046): libfprint-image_device-DEBUG: 17:02:41.301: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.301: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.301: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.301: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.301: started capturer 283s (process:2046): libfprint-device-DEBUG: 17:02:41.301: Device reported finger status change: FP_FINGER_STATUS_NEEDED 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.341: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.342: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.342: stddev=933d, ip=40, is_fp=0, is_empty=2 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.342: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.342: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.385: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.385: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.385: stddev=829d, ip=48, is_fp=0, is_empty=2 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.385: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.385: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.427: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.427: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.428: stddev=1307d, ip=37, is_fp=0, is_empty=2 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.428: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.428: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.468: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.468: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.468: stddev=1163d, ip=38, is_fp=0, is_empty=2 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.468: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.468: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.509: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.509: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.509: stddev=960d, ip=43, is_fp=0, is_empty=2 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.509: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.509: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.547: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.547: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.548: stddev=879d, ip=41, is_fp=0, is_empty=2 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.548: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.548: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.585: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.585: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.585: stddev=925d, ip=44, is_fp=0, is_empty=2 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.585: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.585: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.624: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.624: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.625: stddev=1244d, ip=37, is_fp=0, is_empty=2 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.625: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.625: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.665: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.665: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.665: stddev=709d, ip=48, is_fp=0, is_empty=2 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.665: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.665: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.702: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.702: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.702: stddev=553d, ip=54, is_fp=0, is_empty=2 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.702: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.702: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.739: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.740: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.740: stddev=904d, ip=44, is_fp=0, is_empty=2 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.740: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.740: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.777: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.777: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.777: stddev=951d, ip=46, is_fp=0, is_empty=2 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.777: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.777: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.813: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.813: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.814: stddev=795d, ip=44, is_fp=0, is_empty=2 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.814: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.814: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.851: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.851: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.851: stddev=985d, ip=41, is_fp=0, is_empty=2 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.851: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.851: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.889: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.889: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.890: stddev=938d, ip=40, is_fp=0, is_empty=2 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.890: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.890: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.929: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.929: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.929: stddev=846d, ip=40, is_fp=0, is_empty=2 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.929: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.929: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.969: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.969: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 283s (process:2046): libfprint-elanspi-DEBUG: 17:02:41.969: stddev=693d, ip=56, is_fp=0, is_empty=2 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.969: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 283s (process:2046): libfprint-SSM-DEBUG: 17:02:41.969: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.006: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.006: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.007: stddev=777d, ip=50, is_fp=0, is_empty=2 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.007: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.007: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.044: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.044: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.044: stddev=824d, ip=45, is_fp=0, is_empty=2 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.044: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.044: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.081: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.081: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.081: stddev=521d, ip=50, is_fp=0, is_empty=2 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.081: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.082: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.118: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.118: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.119: stddev=670d, ip=47, is_fp=0, is_empty=2 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.119: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.119: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.157: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.157: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.157: stddev=1262d, ip=39, is_fp=0, is_empty=2 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.157: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.157: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.196: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.197: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.197: stddev=912d, ip=42, is_fp=0, is_empty=2 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.197: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.197: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.236: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.236: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.237: stddev=1402d, ip=37, is_fp=0, is_empty=2 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.237: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.237: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.275: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.275: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.275: stddev=1530d, ip=32, is_fp=0, is_empty=2 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.275: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.275: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.311: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.311: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.311: stddev=718159d, ip=6, is_fp=1, is_empty=0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.311: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.311: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.349: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.349: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.350: stddev=400929d, ip=0, is_fp=2, is_empty=0 284s (process:2046): libfprint-device-DEBUG: 17:02:42.350: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 284s (process:2046): libfprint-image_device-DEBUG: 17:02:42.350: Image device reported finger status: on 284s (process:2046): libfprint-image_device-DEBUG: 17:02:42.350: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.350: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.350: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.388: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.388: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.389: stddev=346514d, ip=0, is_fp=1, is_empty=0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.389: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.389: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.427: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.427: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.427: stddev=324160d, ip=0, is_fp=1, is_empty=0 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.428: diff = 107344 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.428: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.428: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.464: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.465: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.465: stddev=339430d, ip=0, is_fp=1, is_empty=0 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.466: diff = 246471 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.466: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.466: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.502: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.502: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.502: stddev=334711d, ip=0, is_fp=1, is_empty=0 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.503: diff = 73010 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.503: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.503: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.539: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.539: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.539: stddev=317574d, ip=0, is_fp=1, is_empty=0 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.540: diff = 58831 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.540: ignoring b.c. difference is too small 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.540: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.540: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.576: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.576: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.576: stddev=285577d, ip=0, is_fp=1, is_empty=0 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.577: diff = 241923 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.577: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.577: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.612: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.613: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.613: stddev=417772d, ip=0, is_fp=2, is_empty=0 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.614: diff = 254823 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.614: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.614: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.650: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.650: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.650: stddev=541148d, ip=0, is_fp=2, is_empty=0 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.651: diff = 290922 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.651: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.651: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.687: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.687: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.687: stddev=580192d, ip=0, is_fp=2, is_empty=0 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.688: diff = 332283 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.688: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.688: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.725: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.725: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.725: stddev=484527d, ip=0, is_fp=2, is_empty=0 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.726: diff = 325141 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.726: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.726: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.762: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.762: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.762: stddev=482100d, ip=0, is_fp=2, is_empty=0 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.763: diff = 337412 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.763: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.763: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.799: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.799: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.800: stddev=558238d, ip=0, is_fp=2, is_empty=0 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.800: diff = 342841 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.800: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.800: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.837: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.837: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.837: stddev=572990d, ip=0, is_fp=2, is_empty=0 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.838: diff = 352690 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.838: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.838: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.874: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.874: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.875: stddev=575411d, ip=0, is_fp=2, is_empty=0 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.875: diff = 365537 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.875: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.875: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.911: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.911: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.911: stddev=578482d, ip=0, is_fp=2, is_empty=0 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.912: diff = 342041 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.912: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.912: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.948: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.948: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.948: stddev=572686d, ip=0, is_fp=2, is_empty=0 284s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.949: diff = 421037 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.949: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 284s (process:2046): libfprint-SSM-DEBUG: 17:02:42.949: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 285s (process:2046): libfprint-SSM-DEBUG: 17:02:42.984: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 285s (process:2046): libfprint-SSM-DEBUG: 17:02:42.985: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 285s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.985: stddev=465498d, ip=0, is_fp=2, is_empty=0 285s (process:2046): libfprint-elanspi-DEBUG: 17:02:42.986: diff = 404640 285s (process:2046): libfprint-SSM-DEBUG: 17:02:42.986: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 285s (process:2046): libfprint-SSM-DEBUG: 17:02:42.986: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.022: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.022: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 285s (process:2046): libfprint-elanspi-DEBUG: 17:02:43.023: stddev=410135d, ip=0, is_fp=2, is_empty=0 285s (process:2046): libfprint-elanspi-DEBUG: 17:02:43.023: diff = 347658 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.023: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.023: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.060: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.060: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 285s (process:2046): libfprint-elanspi-DEBUG: 17:02:43.060: stddev=493239d, ip=0, is_fp=2, is_empty=0 285s (process:2046): libfprint-elanspi-DEBUG: 17:02:43.061: diff = 344237 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.061: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.061: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.097: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.097: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 285s (process:2046): libfprint-elanspi-DEBUG: 17:02:43.097: stddev=553028d, ip=0, is_fp=2, is_empty=0 285s (process:2046): libfprint-elanspi-DEBUG: 17:02:43.098: diff = 419597 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.098: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.098: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.134: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.134: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 285s (process:2046): libfprint-elanspi-DEBUG: 17:02:43.134: stddev=574502d, ip=0, is_fp=2, is_empty=0 285s (process:2046): libfprint-elanspi-DEBUG: 17:02:43.135: diff = 408934 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.135: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.135: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.171: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.171: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 285s (process:2046): libfprint-elanspi-DEBUG: 17:02:43.172: stddev=645815d, ip=0, is_fp=2, is_empty=0 285s (process:2046): libfprint-elanspi-DEBUG: 17:02:43.172: diff = 409198 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.172: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.172: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.208: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.208: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 285s (process:2046): libfprint-elanspi-DEBUG: 17:02:43.209: stddev=677451d, ip=0, is_fp=2, is_empty=0 285s (process:2046): libfprint-elanspi-DEBUG: 17:02:43.209: diff = 429666 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.209: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.209: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.246: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.246: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 285s (process:2046): libfprint-elanspi-DEBUG: 17:02:43.246: stddev=634407d, ip=0, is_fp=2, is_empty=0 285s (process:2046): libfprint-elanspi-DEBUG: 17:02:43.246: have enough frames, exiting now 285s (process:2046): libfprint-assembling-DEBUG: 17:02:43.407: calc delta completed in 0.160281 secs 285s (process:2046): libfprint-assembling-DEBUG: 17:02:43.567: calc delta completed in 0.160621 secs 285s (process:2046): libfprint-assembling-DEBUG: 17:02:43.567: errors: 86516 rev: 170625 285s (process:2046): libfprint-assembling-DEBUG: 17:02:43.727: calc delta completed in 0.159970 secs 285s (process:2046): libfprint-assembling-DEBUG: 17:02:43.728: height is 246 285s (process:2046): libfprint-image_device-DEBUG: 17:02:43.730: Image device captured an image 285s (process:2046): libfprint-image_device-DEBUG: 17:02:43.730: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 285s (process:2046): libfprint-device-DEBUG: 17:02:43.731: Device reported finger status change: FP_FINGER_STATUS_PRESENT 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.731: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.731: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.780: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.780: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 285s (process:2046): libfprint-elanspi-DEBUG: 17:02:43.780: stddev=593525d, ip=0, is_fp=2, is_empty=0 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.780: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.780: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 285s (process:2046): libfprint-image-DEBUG: 17:02:43.832: Minutiae scan completed in 0.102210 secs 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.833: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.833: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 285s (process:2046): libfprint-elanspi-DEBUG: 17:02:43.833: stddev=610651d, ip=0, is_fp=2, is_empty=0 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.833: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.833: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.870: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.870: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 285s (process:2046): libfprint-elanspi-DEBUG: 17:02:43.870: stddev=505673d, ip=0, is_fp=2, is_empty=0 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.870: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.870: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.908: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.908: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 285s (process:2046): libfprint-elanspi-DEBUG: 17:02:43.908: stddev=537580d, ip=0, is_fp=2, is_empty=0 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.908: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.908: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.947: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.947: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 285s (process:2046): libfprint-elanspi-DEBUG: 17:02:43.948: stddev=520750d, ip=0, is_fp=2, is_empty=0 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.948: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 285s (process:2046): libfprint-SSM-DEBUG: 17:02:43.948: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:43.985: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 286s (process:2046): libfprint-SSM-DEBUG: 17:02:43.985: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 286s (process:2046): libfprint-elanspi-DEBUG: 17:02:43.985: stddev=468008d, ip=0, is_fp=2, is_empty=0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:43.985: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 286s (process:2046): libfprint-SSM-DEBUG: 17:02:43.985: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.022: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.022: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 286s (process:2046): libfprint-elanspi-DEBUG: 17:02:44.022: stddev=477058d, ip=0, is_fp=2, is_empty=0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.022: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.022: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.060: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.060: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 286s (process:2046): libfprint-elanspi-DEBUG: 17:02:44.060: stddev=460178d, ip=0, is_fp=2, is_empty=0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.060: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.060: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.097: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.097: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 286s (process:2046): libfprint-elanspi-DEBUG: 17:02:44.097: stddev=538508d, ip=0, is_fp=2, is_empty=0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.097: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.097: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.134: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.134: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 286s (process:2046): libfprint-elanspi-DEBUG: 17:02:44.135: stddev=661673d, ip=0, is_fp=2, is_empty=0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.135: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.135: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.171: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.171: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 286s (process:2046): libfprint-elanspi-DEBUG: 17:02:44.171: stddev=764706d, ip=0, is_fp=2, is_empty=0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.171: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.171: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.210: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.210: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 286s (process:2046): libfprint-elanspi-DEBUG: 17:02:44.210: stddev=806415d, ip=0, is_fp=2, is_empty=0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.210: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.210: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.247: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.247: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 286s (process:2046): libfprint-elanspi-DEBUG: 17:02:44.247: stddev=806649d, ip=0, is_fp=2, is_empty=0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.247: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.248: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.284: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.285: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 286s (process:2046): libfprint-elanspi-DEBUG: 17:02:44.285: stddev=822567d, ip=0, is_fp=2, is_empty=0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.285: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.285: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.322: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.322: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 286s (process:2046): libfprint-elanspi-DEBUG: 17:02:44.322: stddev=1017068d, ip=0, is_fp=2, is_empty=0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.323: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.323: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.359: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.359: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 286s (process:2046): libfprint-elanspi-DEBUG: 17:02:44.359: stddev=1004196d, ip=0, is_fp=2, is_empty=0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.359: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.359: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.395: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.396: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 286s (process:2046): libfprint-elanspi-DEBUG: 17:02:44.396: stddev=963655d, ip=0, is_fp=2, is_empty=0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.396: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.396: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.432: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.432: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 286s (process:2046): libfprint-elanspi-DEBUG: 17:02:44.433: stddev=880521d, ip=0, is_fp=2, is_empty=0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.433: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.433: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.469: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.470: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 286s (process:2046): libfprint-elanspi-DEBUG: 17:02:44.470: stddev=1135372d, ip=0, is_fp=2, is_empty=0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.470: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.470: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.508: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.508: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 286s (process:2046): libfprint-elanspi-DEBUG: 17:02:44.509: stddev=1093450d, ip=3, is_fp=1, is_empty=0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.509: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.509: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.545: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.545: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 286s (process:2046): libfprint-elanspi-DEBUG: 17:02:44.546: stddev=41090d, ip=8, is_fp=0, is_empty=2 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.546: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.546: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.583: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.583: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 286s (process:2046): libfprint-elanspi-DEBUG: 17:02:44.583: stddev=6836d, ip=13, is_fp=0, is_empty=2 286s (process:2046): libfprint-device-DEBUG: 17:02:44.583: Device reported finger status change: FP_FINGER_STATUS_NONE 286s (process:2046): libfprint-image_device-DEBUG: 17:02:44.583: Image device reported finger status: off 286s (process:2046): libfprint-image_device-DEBUG: 17:02:44.583: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 286s (process:2046): libfprint-image_device-DEBUG: 17:02:44.583: Deactivating image device 286s (process:2046): libfprint-image_device-DEBUG: 17:02:44.583: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 286s (process:2046): libfprint-image_device-DEBUG: 17:02:44.583: Image device deactivation completed 286s (process:2046): libfprint-image_device-DEBUG: 17:02:44.583: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 286s (process:2046): libfprint-device-DEBUG: 17:02:44.583: Device reported capture completion 286s (process:2046): libfprint-SSM-DEBUG: 17:02:44.583: [elanspi] ELANSPI_FPCAPT_NSTATES completed successfully 286s (process:2046): libfprint-device-DEBUG: 17:02:44.583: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 286s (process:2046): libfprint-device-DEBUG: 17:02:44.583: Updated temperature model after 3.36 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 286s (process:2046): libfprint-image_device-DEBUG: 17:02:44.584: Image device close completed 286s (process:2046): libfprint-device-DEBUG: 17:02:44.584: Device reported close completion 286s (process:2046): libfprint-device-DEBUG: 17:02:44.584: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 286s (process:2046): libfprint-device-DEBUG: 17:02:44.584: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 286s ** (umockdev-run:2042): DEBUG: 17:02:44.777: umockdev.vala:150: Removing test bed /tmp/umockdev.FSLBK2 286s (umockdev-run:2042): GLib-DEBUG: 17:02:44.783: unsetenv() is not thread-safe and should not be used after threads are created 286s Comparing PNGs /tmp/libfprint-umockdev-test-rg8yrn8y/capture.png and /usr/share/installed-tests/libfprint-2/elanspi/capture.png 286s PASS: libfprint-2/driver-elanspi.test 286s Running test: libfprint-2/driver-vfs0050.test 286s ** (umockdev-run:2057): DEBUG: 17:02:44.879: umockdev.vala:123: Created udev test bed /tmp/umockdev.AAL4J2 286s ** (umockdev-run:2057): DEBUG: 17:02:44.879: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 286s ** (umockdev-run:2057): DEBUG: 17:02:44.880: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 286s ** (umockdev-run:2057): DEBUG: 17:02:44.882: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.AAL4J2/dev/bus/usb/001/004 286s ** (umockdev-run:2057): DEBUG: 17:02:44.882: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 286s ** (umockdev-run:2057): DEBUG: 17:02:44.883: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 286s ** (umockdev-run:2057): DEBUG: 17:02:44.885: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.AAL4J2/dev/bus/usb/001/001 286s ** (umockdev-run:2057): DEBUG: 17:02:44.885: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 286s ** (umockdev-run:2057): DEBUG: 17:02:44.886: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 286s (umockdev-run:2057): GLib-GIO-DEBUG: 17:02:44.887: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 286s (process:2061): libfprint-context-DEBUG: 17:02:44.954: Initializing FpContext (libfprint version 1.94.7+tod1) 286s (process:2061): libfprint-tod-DEBUG: 17:02:44.954: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 286s (process:2061): libfprint-context-DEBUG: 17:02:44.956: No driver found for USB device 1D6B:0002 286s (process:2061): libfprint-device-DEBUG: 17:02:44.956: Device reported probe completion 286s (process:2061): libfprint-device-DEBUG: 17:02:44.956: Completing action FPI_DEVICE_ACTION_PROBE in idle! 286s (process:2061): libfprint-device-DEBUG: 17:02:44.956: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s libusb: error [op_handle_events] cannot find handle for fd 9 286s libusb: error [op_handle_events] cannot find handle for fd 9 286s libusb: error [op_handle_events] cannot find handle for fd 9 286s libusb: error [op_handle_events] cannot find handle for fd 9 286s libusb: error [op_handle_events] cannot find handle for fd 9 286s libusb: error [op_handle_events] cannot find handle for fd 9 286s libusb: error [op_handle_events] cannot find handle for fd 9 286s libusb: error [op_handle_events] cannot find handle for fd 9 286s libusb: error [op_handle_events] cannot find handle for fd 9 286s libusb: error [op_handle_events] cannot find handle for fd 9 286s libusb: error [op_handle_events] cannot find handle for fd 9 286s libusb: error [op_handle_events] cannot find handle for fd 9 286s libusb: error [op_handle_events] cannot find handle for fd 9 286s libusb: error [op_handle_events] cannot find handle for fd 9 286s libusb: error [op_handle_events] cannot find handle for fd 9 286s libusb: error [op_handle_events] cannot find handle for fd 9 286s libusb: error [op_handle_events] cannot find handle for fd 9 286s libusb: error [op_handle_events] cannot find handle for fd 9 286s libusb: error [op_handle_events] cannot find handle for fd 9 286s libusb: error [op_handle_events] cannot find handle for fd 9 286s libusb: error [op_handle_events] cannot find handle for fd 9 286s libusb: error [op_handle_events] cannot find handle for fd 9 286s libusb: error [op_handle_events] cannot find handle for fd 9 286s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find ha(process:2061): libfprint-SSM-DEBUG: 17:02:44.959: [vfs0050] SSM_STATES entering state 0 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.960: [vfs0050] SSM_STATES entering state 1 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.960: [vfs0050] SSM_STATES entering state 2 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.961: [vfs0050] SSM_STATES entering state 3 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.961: [vfs0050] SUBSM1_STATES entering state 0 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.961: [vfs0050] SUBSM1_STATES entering state 1 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.962: [vfs0050] SUBSM1_STATES entering state 2 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.962: [vfs0050] SUBSM1_STATES completed successfully 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.962: [vfs0050] SSM_STATES entering state 4 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.962: [vfs0050] SUBSM2_STATES entering state 0 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.963: [vfs0050] SUBSM2_STATES entering state 1 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.963: [vfs0050] SUBSM2_STATES entering state 2 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.964: [vfs0050] SUBSM2_STATES entering state 3 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.964: [vfs0050] SUBSM2_STATES entering state 4 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.965: [vfs0050] SUBSM2_STATES entering state 5 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.965: [vfs0050] SUBSM2_STATES entering state 6 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.965: [vfs0050] SUBSM1_STATES entering state 0 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.965: [vfs0050] SUBSM1_STATES entering state 1 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.966: [vfs0050] SUBSM1_STATES entering state 2 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.966: [vfs0050] SUBSM1_STATES completed successfully 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.966: [vfs0050] SUBSM2_STATES completed successfully 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.966: [vfs0050] SSM_STATES entering state 5 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.967: [vfs0050] SSM_STATES completed successfully 287s (process:2061): libfprint-image_device-DEBUG: 17:02:44.967: Image device open completed 287s (process:2061): libfprint-device-DEBUG: 17:02:44.967: Device reported open completion 287s (process:2061): libfprint-device-DEBUG: 17:02:44.967: Completing action FPI_DEVICE_ACTION_OPEN in idle! 287s ndle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s (process:2061): libfprint-device-DEBUG: 17:02:44.967: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 287s (process:2061): libfprint-device-DEBUG: 17:02:44.967: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 287s (process:2061): libfprint-image_device-DEBUG: 17:02:44.967: Activating image device 287s (process:2061): libfprint-image_device-DEBUG: 17:02:44.967: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.967: [vfs0050] SSM_STATES entering state 0 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.968: [vfs0050] SSM_STATES entering state 1 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.968: [vfs0050] SSM_STATES entering state 2 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.969: [vfs0050] SSM_STATES entering state 3 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.969: [vfs0050] SUBSM1_STATES entering state 0 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.969: [vfs0050] SUBSM1_STATES entering state 1 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.970: [vfs0050] SUBSM1_STATES entering state 2 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.970: [vfs0050] SUBSM1_STATES completed successfully 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.970: [vfs0050] SSM_STATES entering state 4 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.970: [vfs0050] SUBSM2_STATES entering state 0 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.971: [vfs0050] SUBSM2_STATES entering state 1 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.971: [vfs0050] SUBSM2_STATES entering state 2 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.971: [vfs0050] SUBSM2_STATES entering state 3 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.972: [vfs0050] SUBSM2_STATES entering state 4 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.972: [vfs0050] SUBSM2_STATES entering state 5 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.973: [vfs0050] SUBSM2_STATES entering state 6 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.973: [vfs0050] SUBSM1_STATES entering state 0 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.973: [vfs0050] SUBSM1_STATES entering state 1 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.974: [vfs0050] SUBSM1_STATES entering state 2 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.974: [vfs0050] SUBSM1_STATES completed successfully 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.974: [vfs0050] SUBSM2_STATES completed successfully 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.974: [vfs0050] SSM_STATES entering state 5 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.974: [vfs0050] SUBSM2_STATES entering state 0 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.975: [vfs0050] SUBSM2_STATES entering state 1 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.975: [vfs0050] SUBSM2_STATES entering state 2 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.975: [vfs0050] SUBSM2_STATES entering state 3 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.976: [vfs0050] SUBSM2_STATES entering state 4 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.976: [vfs0050] SUBSM2_STATES entering state 5 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.977: [vfs0050] SUBSM2_STATES entering state 6 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.977: [vfs0050] SUBSM2_STATES completed successfully 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.977: [vfs0050] SSM_STATES entering state 6 287s (process:2061): libfprint-image_device-DEBUG: 17:02:44.977: Image device activation completed 287s (process:2061): libfprint-image_device-DEBUG: 17:02:44.977: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 287s (process:2061): libfprint-image_device-DEBUG: 17:02:44.977: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 287s (process:2061): libfprint-device-DEBUG: 17:02:44.977: Device reported finger status change: FP_FINGER_STATUS_NEEDED 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.977: [vfs0050] SSM_STATES entering state 7 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.977: [vfs0050] SSM_STATES entering state 8 287s (process:2061): libfprint-device-DEBUG: 17:02:44.977: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 287s (process:2061): libfprint-image_device-DEBUG: 17:02:44.977: Image device reported finger status: on 287s (process:2061): libfprint-image_device-DEBUG: 17:02:44.977: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.978: [vfs0050] SSM_STATES entering state 8 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.978: [vfs0050] SSM_STATES entering state 8 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.979: [vfs0050] SSM_STATES entering state 8 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.980: [vfs0050] SSM_STATES entering state 8 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.980: [vfs0050] SSM_STATES entering state 8 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.981: [vfs0050] SSM_STATES entering state 8 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.981: [vfs0050] SSM_STATES entering state 8 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.982: [vfs0050] SSM_STATES entering state 8 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.983: [vfs0050] SSM_STATES entering state 8 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.983: [vfs0050] SSM_STATES entering state 8 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.984: [vfs0050] SSM_STATES entering state 8 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.984: [vfs0050] SSM_STATES entering state 8 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.985: [vfs0050] SSM_STATES entering state 8 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.986: [vfs0050] SSM_STATES entering state 8 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.986: [vfs0050] SSM_STATES entering state 8 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.987: [vfs0050] SSM_STATES entering state 8 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.987: [vfs0050] SSM_STATES entering state 8 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.988: [vfs0050] SSM_STATES entering state 8 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.988: [vfs0050] SSM_STATES entering state 8 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.989: [vfs0050] SSM_STATES entering state 8 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.989: [vfs0050] SSM_STATES entering state 8 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.990: [vfs0050] SSM_STATES entering state 8 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.991: [vfs0050] SSM_STATES entering state 8 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.992: [vfs0050] SSM_STATES entering state 8 287s (process:2061): libfprint-SSM-DEBUG: 17:02:44.992: [vfs0050] SSM_STATES entering state 9 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 1709917364992556 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 1 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 1 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 2 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 1 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 51 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 9 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 7 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 5 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 3 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 1 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 8 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 35 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 2 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 9 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 7 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 5 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 3 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 1 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 8 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 4 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 2 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 38 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 8 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 4 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 98 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 94 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 92 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 90 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 98 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 98 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 97 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 95 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 93 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 98 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 94 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 92 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 90 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 88 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 86 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 84 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 98 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 97 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 70 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 66 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 64 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 97 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 8 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 4 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 2 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 8 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 4 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 2 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 3 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 98 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 98 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 94 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 98 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 94 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 92 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 90 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 88 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 86 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 84 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 97 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 95 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 93 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 97 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 95 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 93 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 91 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 89 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 87 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.992: 85 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 83 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 87 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 85 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 83 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 81 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 79 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 81 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 79 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 77 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 79 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 77 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 75 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 79 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 75 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 79 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 77 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 75 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 73 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 71 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 71 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 69 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 70 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 66 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 64 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 66 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 64 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 62 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 60 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 58 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 60 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 62 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 61 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 57 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 58 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 56 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 54 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 52 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 50 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 57 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 54 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 57 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 54 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 54 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 56 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 58 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 56 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 54 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 54 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 52 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 53 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 52 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 50 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 48 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 54 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 54 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 53 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 54 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 53 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 52 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 52 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 50 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 50 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 50 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 49 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 49 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 48 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 49 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 47 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 46 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 45 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 44 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 44 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 44 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 44 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 44 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 44 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 46 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 47 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 47 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 46 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 46 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 44 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 44 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 43 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 43 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 43 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 43 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 43 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 43 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 43 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 39 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 38 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 39 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 38 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 38 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 38 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 37 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 38 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 35 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 35 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 35 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 35 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 35 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 35 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 35 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 35 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 35 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 35 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 61 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.993: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 1 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 91 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 89 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 86 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 60 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 60 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 62 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 61 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 57 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 57 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 56 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 53 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 51 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 46 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 53 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 93 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 92 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 92 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.994: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 75 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 74 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 37 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 54 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 73 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 71 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.995: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.996: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.996: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.996: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.996: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.996: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.996: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.996: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.996: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.996: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.996: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.996: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.996: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.997: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.997: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.997: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.997: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.997: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.997: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.997: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.997: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.997: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.997: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.997: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.998: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.998: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.998: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.998: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.998: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.998: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.998: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.998: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.998: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.998: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.998: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.998: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.998: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.998: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.998: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.998: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.998: 52 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.998: 51 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.998: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.998: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.998: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.998: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.998: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 84 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 45 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:44.999: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 38 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 79 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 9 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 67 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 66 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 66 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 98 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.000: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 9 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 9 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 9 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 9 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 7 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 9 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 9 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 50 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 61 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 83 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 38 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 9 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 92 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 69 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.001: 67 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.002: 66 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.002: 92 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.002: 90 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.002: 79 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.002: 73 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.002: 71 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.002: 70 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.002: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.002: 67 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.002: 89 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.002: 87 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 90 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 88 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 86 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 37 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 53 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 75 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 73 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 76 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 74 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 39 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 48 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 64 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 62 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 83 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 86 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 52 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 50 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 71 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 76 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 70 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 7 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 7 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.003: 8 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 4 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 51 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 9 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 7 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 98 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 92 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 90 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 95 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 94 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 92 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 83 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 81 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 97 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 98 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 89 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 87 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 70 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 97 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 81 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 98 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 77 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 53 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 51 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 49 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 47 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 45 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 43 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 38 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 37 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 35 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.004: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 9 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 7 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 44 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 52 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 98 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 71 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 3 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 70 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 77 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 85 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 60 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 58 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 4 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 51 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 63 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 69 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 74 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 51 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 61 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 93 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 83 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 81 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 48 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 77 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 39 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 93 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 35 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 85 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 83 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 86 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 4 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 77 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 80 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 51 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 74 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 72 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 45 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 43 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 66 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 3 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 37 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 60 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 53 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 56 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 54 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 47 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 50 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 44 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 56 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 58 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 62 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 8 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 4 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 93 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 53 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 51 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 52 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 47 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 93 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 46 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 89 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 52 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 91 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 73 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 46 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 69 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 65 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 69 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 4 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 2 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 86 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 87 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 9 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 92 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 1 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 39 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 7 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 50 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 89 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 92 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 3 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 39 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 89 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 75 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 73 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 81 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 75 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 70 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 57 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 44 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 62 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 94 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 56 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 91 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 93 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 44 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 89 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 76 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 38 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 72 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 66 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 3 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 83 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 49 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 5 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 3 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 4 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 38 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 37 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 98 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 81 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 88 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 88 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 89 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 9 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 75 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 3 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 71 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 80 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 67 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 76 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 74 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 52 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 79 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 77 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 97 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 1 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 45 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 84 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 5 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 83 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 81 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 74 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 1 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 75 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 73 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 66 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 69 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 67 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 65 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 61 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 57 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 9 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 53 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 51 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 100 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 1 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 95 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 88 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 86 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 5 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 93 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 75 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 81 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 9 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 77 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 67 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 73 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 69 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 50 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 67 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 65 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 63 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 84 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 95 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 53 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 65 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 84 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 65 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 45 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 39 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 58 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 35 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 63 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 54 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 49 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 9 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 9 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 7 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 5 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 1 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 37 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 5 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 3 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 8 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 1 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 4 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 7 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 7 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 4 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 2 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 1 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 2 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 4 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 2 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.005: 1 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: offsets_filtered: 1709917365007032 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 5 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 5 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 7 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 7 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 8 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 8 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 9 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 9 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 9 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.007: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 90 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 92 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 94 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.008: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 97 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 97 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 97 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 97 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 95 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 94 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 93 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 92 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 90 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 88 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 86 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 84 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 70 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 97 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.009: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 99 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 98 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 98 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 98 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 97 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 97 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 96 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 95 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 95 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 94 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 94 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 93 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 93 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 92 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 91 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 90 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 89 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 88 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 87 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 87 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 86 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 85 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 85 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 84 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 83 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.010: 83 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 81 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 81 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 79 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 79 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 79 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 79 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 79 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 77 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 77 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 77 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 75 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 75 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 75 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 73 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 71 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 71 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 70 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 69 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 66 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 66 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 64 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 64 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 62 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 62 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 61 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 60 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 60 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 58 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 58 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 57 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 57 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 57 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 57 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 56 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 56 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 56 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 54 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 54 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 54 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 54 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 54 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 54 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 54 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 54 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 54 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 54 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 54 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 53 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 53 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 53 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 52 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 52 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 52 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 52 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 50 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.011: 50 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 50 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 50 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 49 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 49 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 49 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 49 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 48 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 47 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 47 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 47 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 46 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 46 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 46 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 46 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 45 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 44 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 44 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 44 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 44 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 44 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 44 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 44 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 44 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 43 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 43 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 43 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 43 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 43 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.012: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 39 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 39 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 38 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 38 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 38 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 38 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 38 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 37 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 35 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 35 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 35 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 35 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 35 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 35 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 35 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 35 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 35 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.013: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.014: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 30 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.015: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 19 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 18 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 16 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 11 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 12 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 38 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 50 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 61 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 66 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 67 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 67 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 69 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 70 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 70 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 70 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 71 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 71 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 73 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 73 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 73 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 73 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 73 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 73 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 73 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 73 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 73 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 71 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 70 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 70 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 67 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 67 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 64 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 64 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 62 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 53 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 53 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 52 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 52 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 50 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 48 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 51 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 51 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 81 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 83 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 90 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 92 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 92 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 92 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 92 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 92 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 92 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 94 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 94 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 94 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 94 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 92 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 92 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 90 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 89 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 87 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 83 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 81 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 81 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 77 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 70 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 53 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 51 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 49 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 47 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 45 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 43 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 38 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 37 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.016: 35 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 20 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 24 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 51 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 51 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 58 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 58 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 58 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 58 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 60 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 60 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 60 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 61 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 61 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 61 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 61 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 60 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 53 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 53 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 54 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 53 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 53 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 51 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 51 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 51 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 51 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 51 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 50 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 47 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 50 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 50 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 47 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 47 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 45 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 44 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 43 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 42 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 36 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 46 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 46 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 46 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 46 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 46 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 46 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 46 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 46 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 46 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 47 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 47 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 47 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 47 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 51 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 51 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 47 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 46 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 46 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 32 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 26 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 23 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 25 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 39 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 39 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 39 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 39 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 50 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 57 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 57 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 62 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 62 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 62 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 62 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 57 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 57 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 57 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 56 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 56 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 56 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 44 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 49 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 44 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 38 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 38 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 38 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 38 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 37 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 37 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 37 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 37 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 37 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 38 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 52 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 52 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 45 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 52 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 52 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 52 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 67 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 71 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 73 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 71 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 71 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 69 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 68 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 67 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 66 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 66 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 66 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 65 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 61 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 65 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 61 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 65 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 66 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 66 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 65 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 66 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 66 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 65 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 61 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 59 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 57 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 53 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 51 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 33 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 34 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 50 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 50 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 50 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 63 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 63 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 63 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 63 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 65 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.017: 65 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.018: 65 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.018: 65 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.018: 65 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.018: 65 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.018: 65 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.018: 65 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.018: 63 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.018: 58 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.018: 58 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.018: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.018: 55 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.018: 53 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.018: 50 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 53 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 45 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 45 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 41 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 40 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 39 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 35 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 31 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 29 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 28 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 27 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 22 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 21 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 17 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 15 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 14 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 13 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 10 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 9 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 9 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 8 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 7 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 7 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 7 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.019: 4 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.020: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.020: 6 287s (process:2061): libfprint-assembling-DEBUG: 17:02:45.020: 1 287s (process:2061): libfprint-image_device-DEBUG: 17:02:45.023: Image device captured an image 287s (process:2061): libfprint-image_device-DEBUG: 17:02:45.024: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 287s (process:2061): libfprint-device-DEBUG: 17:02:45.024: Device reported finger status change: FP_FINGER_STATUS_PRESENT 287s (process:2061): libfprint-device-DEBUG: 17:02:45.024: Device reported finger status change: FP_FINGER_STATUS_NONE 287s (process:2061): libfprint-image_device-DEBUG: 17:02:45.024: Image device reported finger status: off 287s (process:2061): libfprint-image_device-DEBUG: 17:02:45.024: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 287s (process:2061): libfprint-image_device-DEBUG: 17:02:45.024: Deactivating image device 287s (process:2061): libfprint-image_device-DEBUG: 17:02:45.024: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 287s (process:2061): libfprint-device-DEBUG: 17:02:45.069: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 287s (process:2061): libfprint-SSM-DEBUG: 17:02:45.093: [vfs0050] SSM_STATES entering state 10 287s (process:2061): libfprint-SSM-DEBUG: 17:02:45.093: [vfs0050] SSM_STATES entering state 3 287s (process:2061): libfprint-SSM-DEBUG: 17:02:45.093: [vfs0050] SUBSM1_STATES entering state 0 287s (process:2061): libfprint-image-DEBUG: 17:02:45.093: Minutiae scan completed in 0.069287 secs 287s (process:2061): libfprint-SSM-DEBUG: 17:02:45.094: [vfs0050] SUBSM1_STATES entering state 1 287s (process:2061): libfprint-SSM-DEBUG: 17:02:45.094: [vfs0050] SUBSM1_STATES entering state 2 287s (process:2061): libfprint-SSM-DEBUG: 17:02:45.095: [vfs0050] SUBSM1_STATES completed successfully 287s (process:2061): libfprint-SSM-DEBUG: 17:02:45.095: [vfs0050] SSM_STATES entering state 4 287s (process:2061): libfprint-SSM-DEBUG: 17:02:45.095: [vfs0050] SUBSM2_STATES entering state 0 287s (process:2061): libfprint-SSM-DEBUG: 17:02:45.095: [vfs0050] SUBSM2_STATES entering state 1 287s (process:2061): libfprint-SSM-DEBUG: 17:02:45.095: [vfs0050] SUBSM2_STATES entering state 2 287s (process:2061): libfprint-SSM-DEBUG: 17:02:45.096: [vfs0050] SUBSM2_STATES entering state 3 287s (process:2061): libfprint-SSM-DEBUG: 17:02:45.096: [vfs0050] SUBSM2_STATES entering state 4 287s (process:2061): libfprint-SSM-DEBUG: 17:02:45.097: [vfs0050] SUBSM2_STATES entering state 5 287s (process:2061): libfprint-SSM-DEBUG: 17:02:45.097: [vfs0050] SUBSM2_STATES entering state 6 287s (process:2061): libfprint-SSM-DEBUG: 17:02:45.097: [vfs0050] SUBSM1_STATES entering state 0 287s (process:2061): libfprint-SSM-DEBUG: 17:02:45.098: [vfs0050] SUBSM1_STATES entering state 1 287s (process:2061): libfprint-SSM-DEBUG: 17:02:45.098: [vfs0050] SUBSM1_STATES entering state 2 287s (process:2061): libfprint-SSM-DEBUG: 17:02:45.099: [vfs0050] SUBSM1_STATES completed successfully 287s (process:2061): libfprint-SSM-DEBUG: 17:02:45.099: [vfs0050] SUBSM2_STATES completed successfully 287s (process:2061): libfprint-SSM-DEBUG: 17:02:45.099: [vfs0050] SSM_STATES entering state 5 287s (process:2061): libfprint-SSM-DEBUG: 17:02:45.099: [vfs0050] SSM_STATES completed successfully 287s (process:2061): libfprint-image_device-DEBUG: 17:02:45.099: Image device deactivation completed 287s (process:2061): libfprint-image_device-DEBUG: 17:02:45.099: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 287s (process:2061): libfprint-device-DEBUG: 17:02:45.099: Device reported capture completion 287s (process:2061): libfprint-device-DEBUG: 17:02:45.099: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 287s (process:2061): libfprint-device-DEBUG: 17:02:45.099: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 287s (process:2061): libfprint-image_device-DEBUG: 17:02:45.099: Image device close completed 287s (process:2061): libfprint-device-DEBUG: 17:02:45.099: Device reported close completion 287s (process:2061): libfprint-device-DEBUG: 17:02:45.099: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 287s (process:2061): libfprint-device-DEBUG: 17:02:45.099: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 287s ** (umockdev-run:2057): DEBUG: 17:02:45.250: umockdev.vala:150: Removing test bed /tmp/umockdev.AAL4J2 287s (umockdev-run:2057): GLib-DEBUG: 17:02:45.253: unsetenv() is not thread-safe and should not be used after threads are created 287s Comparing PNGs /tmp/libfprint-umockdev-test-lfrl76q8/capture.png and /usr/share/installed-tests/libfprint-2/vfs0050/capture.png 287s PASS: libfprint-2/driver-vfs0050.test 287s Running test: libfprint-2/driver-upektc_img-tcs1s.test 287s ** (umockdev-run:2070): DEBUG: 17:02:45.332: umockdev.vala:123: Created udev test bed /tmp/umockdev.YG2FK2 287s ** (umockdev-run:2070): DEBUG: 17:02:45.333: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-2 287s ** (umockdev-run:2070): DEBUG: 17:02:45.337: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-2 (subsystem usb) 287s ** (umockdev-run:2070): DEBUG: 17:02:45.339: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.YG2FK2/dev/bus/usb/003/004 287s ** (umockdev-run:2070): DEBUG: 17:02:45.339: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3 287s ** (umockdev-run:2070): DEBUG: 17:02:45.342: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3 (subsystem usb) 287s ** (umockdev-run:2070): DEBUG: 17:02:45.344: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.YG2FK2/dev/bus/usb/003/001 287s ** (umockdev-run:2070): DEBUG: 17:02:45.344: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4 287s ** (umockdev-run:2070): DEBUG: 17:02:45.346: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4 (subsystem pci) 287s ** (umockdev-run:2070): DEBUG: 17:02:45.348: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:08.1 287s ** (umockdev-run:2070): DEBUG: 17:02:45.349: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:08.1 (subsystem pci) 287s (process:2074): libfprint-context-DEBUG: 17:02:45.398: Initializing FpContext (libfprint version 1.94.7+tod1) 287s (process:2074): libfprint-tod-DEBUG: 17:02:45.398: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 287s (process:2074): libfprint-context-DEBUG: 17:02:45.400: No driver found for USB device 1D6B:0002 287s (process:2074): libfprint-device-DEBUG: 17:02:45.400: Device reported probe completion 287s (process:2074): libfprint-device-DEBUG: 17:02:45.400: Completing action FPI_DEVICE_ACTION_PROBE in idle! 287s (process:2074): libfprint-device-DEBUG: 17:02:45.400: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 287s (process:2074): libfprint-image_device-DEBUG: 17:02:45.402: Image device open completed 287s (process:2074): libfprint-device-DEBUG: 17:02:45.402: Device reported open completion 287s (process:2074): libfprint-device-DEBUG: 17:02:45.402: Completing action FPI_DEVICE_ACTION_OPEN in idle! 287s (process:2074): libfprint-device-DEBUG: 17:02:45.402: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 287s (process:2074): libfprint-device-DEBUG: 17:02:45.403: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 287s (process:2074): libfprint-image_device-DEBUG: 17:02:45.403: Activating image device 287s (process:2074): libfprint-image_device-DEBUG: 17:02:45.403: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.403: [upektc_img] ACTIVATE_NUM_STATES entering state 0 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.404: [upektc_img] ACTIVATE_NUM_STATES entering state 1 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.404: [upektc_img] ACTIVATE_NUM_STATES entering state 2 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.405: [upektc_img] ACTIVATE_NUM_STATES entering state 3 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.405: [upektc_img] ACTIVATE_NUM_STATES entering state 4 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.406: [upektc_img] ACTIVATE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.406: [upektc_img] ACTIVATE_NUM_STATES entering state 6 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.406: [upektc_img] ACTIVATE_NUM_STATES entering state 7 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.407: [upektc_img] ACTIVATE_NUM_STATES entering state 8 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.407: [upektc_img] ACTIVATE_NUM_STATES entering state 9 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.408: [upektc_img] ACTIVATE_NUM_STATES entering state 10 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.408: [upektc_img] ACTIVATE_NUM_STATES entering state 11 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.408: Sensor type : TCS1x, width x height: 256 x 360 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.408: [upektc_img] ACTIVATE_NUM_STATES completed successfully 287s (process:2074): libfprint-image_device-DEBUG: 17:02:45.408: Image device activation completed 287s (process:2074): libfprint-image_device-DEBUG: 17:02:45.409: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 287s (process:2074): libfprint-image_device-DEBUG: 17:02:45.409: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 287s (process:2074): libfprint-device-DEBUG: 17:02:45.409: Device reported finger status change: FP_FINGER_STATUS_NEEDED 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.409: [upektc_img] CAPTURE_NUM_STATES entering state 0 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.409: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.409: request completed, len: 0000 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.409: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.410: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.410: 18th byte is 0c 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.410: [upektc_img] CAPTURE_NUM_STATES entering state 3 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.410: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.411: request completed, len: 0000 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.411: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.411: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.411: 18th byte is 13 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.411: [upektc_img] CAPTURE_NUM_STATES entering state 3 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.412: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.412: request completed, len: 0000 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.412: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.412: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.412: 18th byte is 00 287s (process:2074): libfprint-device-DEBUG: 17:02:45.412: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.412: [upektc_img] CAPTURE_NUM_STATES entering state 3 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.413: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.413: request completed, len: 0000 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.413: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.414: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.414: response_size is 2052, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.414: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.414: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.414: request completed, len: 07c4 287s (process:2074): libfprint-image_device-DEBUG: 17:02:45.414: Image device reported finger status: on 287s (process:2074): libfprint-image_device-DEBUG: 17:02:45.414: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.414: [upektc_img] CAPTURE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.415: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.415: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.415: response_size is 2052, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.415: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.415: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.415: request completed, len: 07c4 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.415: [upektc_img] CAPTURE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.416: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.416: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.416: response_size is 2052, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.416: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.416: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.417: request completed, len: 07c4 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.417: [upektc_img] CAPTURE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.417: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.418: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.418: response_size is 2052, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.418: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.418: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.418: request completed, len: 07c4 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.418: [upektc_img] CAPTURE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.418: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.419: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.419: response_size is 2052, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.419: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.419: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.419: request completed, len: 07c4 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.419: [upektc_img] CAPTURE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.420: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.420: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.420: response_size is 2052, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.420: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.420: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.421: request completed, len: 07c4 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.421: [upektc_img] CAPTURE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.421: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.422: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.422: response_size is 2052, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.422: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.422: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.422: request completed, len: 07c4 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.422: [upektc_img] CAPTURE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.423: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.423: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.423: response_size is 2052, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.423: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.423: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.424: request completed, len: 07c4 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.424: [upektc_img] CAPTURE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.424: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.425: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.425: response_size is 2052, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.425: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.425: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.425: request completed, len: 07c4 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.425: [upektc_img] CAPTURE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.425: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.426: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.426: response_size is 2052, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.426: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.426: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.426: request completed, len: 07c4 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.426: [upektc_img] CAPTURE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.427: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.427: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.427: response_size is 2052, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.427: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.427: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.428: request completed, len: 07c4 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.428: [upektc_img] CAPTURE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.428: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.429: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.429: response_size is 2052, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.429: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.429: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.429: request completed, len: 07c4 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.429: [upektc_img] CAPTURE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.429: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.430: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.430: response_size is 2052, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.430: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.430: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.430: request completed, len: 07c4 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.430: [upektc_img] CAPTURE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.431: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.431: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.431: response_size is 2052, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.431: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.431: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.432: request completed, len: 07c4 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.432: [upektc_img] CAPTURE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.432: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.432: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.432: response_size is 2052, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.432: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.432: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.433: request completed, len: 07c4 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.433: [upektc_img] CAPTURE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.433: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.434: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.434: response_size is 2052, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.434: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.434: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.434: request completed, len: 07c4 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.434: [upektc_img] CAPTURE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.435: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.435: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.435: response_size is 2052, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.435: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.435: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.436: request completed, len: 07c4 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.436: [upektc_img] CAPTURE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.436: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.436: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.436: response_size is 2052, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.436: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.436: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.437: request completed, len: 07c4 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.437: [upektc_img] CAPTURE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.437: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.438: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.438: response_size is 2052, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.438: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.438: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.438: request completed, len: 07c4 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.438: [upektc_img] CAPTURE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.439: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.439: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.439: response_size is 2052, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.439: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.439: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.439: request completed, len: 07c4 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.439: [upektc_img] CAPTURE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.440: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.440: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.440: response_size is 2052, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.440: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.440: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.441: request completed, len: 07c4 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.441: [upektc_img] CAPTURE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.441: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.442: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.442: response_size is 2052, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.442: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.442: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.442: request completed, len: 07c4 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.442: [upektc_img] CAPTURE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.442: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.443: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.443: response_size is 2052, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.443: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.443: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.443: request completed, len: 07c4 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.443: [upektc_img] CAPTURE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.444: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.444: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.444: response_size is 2052, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.444: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.444: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.445: request completed, len: 07c4 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.445: [upektc_img] CAPTURE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.445: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.445: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.445: response_size is 2052, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.445: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.445: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.446: request completed, len: 07c4 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.446: [upektc_img] CAPTURE_NUM_STATES entering state 5 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.446: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.447: request completed, len: 0040 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.447: response_size is 814, actual_length is 64 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.447: Waiting for rest of transfer 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.447: [upektc_img] CAPTURE_NUM_STATES entering state 1 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.447: request completed, len: 02ee 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.447: Image size is 51840 287s (process:2074): libfprint-image_device-DEBUG: 17:02:45.447: Image device captured an image 287s (process:2074): libfprint-image_device-DEBUG: 17:02:45.448: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 287s (process:2074): libfprint-device-DEBUG: 17:02:45.451: Device reported finger status change: FP_FINGER_STATUS_PRESENT 287s (process:2074): libfprint-device-DEBUG: 17:02:45.451: Device reported finger status change: FP_FINGER_STATUS_NONE 287s (process:2074): libfprint-image_device-DEBUG: 17:02:45.451: Image device reported finger status: off 287s (process:2074): libfprint-image_device-DEBUG: 17:02:45.451: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 287s (process:2074): libfprint-image_device-DEBUG: 17:02:45.451: Deactivating image device 287s (process:2074): libfprint-image_device-DEBUG: 17:02:45.451: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.451: [upektc_img] CAPTURE_NUM_STATES completed successfully 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.451: [upektc_img] DEACTIVATE_NUM_STATES entering state 0 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.451: [upektc_img] DEACTIVATE_NUM_STATES entering state 1 287s (process:2074): libfprint-SSM-DEBUG: 17:02:45.452: [upektc_img] DEACTIVATE_NUM_STATES completed successfully 287s (process:2074): libfprint-upektc_img-DEBUG: 17:02:45.452: Deactivate completed 287s (process:2074): libfprint-image_device-DEBUG: 17:02:45.452: Image device deactivation completed 287s (process:2074): libfprint-image_device-DEBUG: 17:02:45.452: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 287s (process:2074): libfprint-image-DEBUG: 17:02:45.484: Minutiae scan completed in 0.036025 secs 287s (process:2074): libfprint-device-DEBUG: 17:02:45.484: Device reported capture completion 287s (process:2074): libfprint-device-DEBUG: 17:02:45.484: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 287s (process:2074): libfprint-device-DEBUG: 17:02:45.484: Updated temperature model after 0.08 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 287s (process:2074): libfprint-image_device-DEBUG: 17:02:45.484: Image device close completed 287s (process:2074): libfprint-device-DEBUG: 17:02:45.484: Device reported close completion 287s (process:2074): libfprint-device-DEBUG: 17:02:45.485: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 287s (process:2074): libfprint-device-DEBUG: 17:02:45.485: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 287s ** (umockdev-run:2070): DEBUG: 17:02:45.559: umockdev.vala:150: Removing test bed /tmp/umockdev.YG2FK2 287s (umockdev-run:2070): GLib-DEBUG: 17:02:45.563: unsetenv() is not thread-safe and should not be used after threads are created 287s Comparing PNGs /tmp/libfprint-umockdev-test-scjln4go/capture.png and /usr/share/installed-tests/libfprint-2/upektc_img-tcs1s/capture.png 287s PASS: libfprint-2/driver-upektc_img-tcs1s.test 287s Running test: libfprint-2/driver-realtek.test 287s ** (umockdev-run:2083): DEBUG: 17:02:45.625: umockdev.vala:123: Created udev test bed /tmp/umockdev.AXUZJ2 287s ** (umockdev-run:2083): DEBUG: 17:02:45.625: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-4 287s ** (umockdev-run:2083): DEBUG: 17:02:45.626: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-4 (subsystem usb) 287s ** (umockdev-run:2083): DEBUG: 17:02:45.629: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.AXUZJ2/dev/bus/usb/001/005 287s ** (umockdev-run:2083): DEBUG: 17:02:45.629: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 287s ** (umockdev-run:2083): DEBUG: 17:02:45.630: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 287s ** (umockdev-run:2083): DEBUG: 17:02:45.632: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.AXUZJ2/dev/bus/usb/001/001 287s ** (umockdev-run:2083): DEBUG: 17:02:45.632: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 287s ** (umockdev-run:2083): DEBUG: 17:02:45.632: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 287s (process:2087): libfprint-context-DEBUG: 17:02:45.679: Initializing FpContext (libfprint version 1.94.7+tod1) 287s (process:2087): libfprint-tod-DEBUG: 17:02:45.680: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 287s (process:2087): libfprint-context-DEBUG: 17:02:45.681: No driver found for USB device 1D6B:0002 287s (process:2087): libfprint-realtek-DEBUG: 17:02:45.682: 121667216: ../libfprint/drivers/realtek/realtek.c:1059 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find ha(process:2087): libfprint-realtek-DEBUG: 17:02:45.685: Device name: Realtek USB2.0 Finger Print Bridge 287s (process:2087): libfprint-device-DEBUG: 17:02:45.686: Device reported probe completion 287s (process:2087): libfprint-device-DEBUG: 17:02:45.686: Completing action FPI_DEVICE_ACTION_PROBE in idle! 287s (process:2087): libfprint-device-DEBUG: 17:02:45.686: Not updating temperature model, device can run continuously! 287s (process:2087): libfprint-realtek-DEBUG: 17:02:45.687: 121672406: ../libfprint/drivers/realtek/realtek.c:1104 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.687: [realtek] Init entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.687: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.688: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.688: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s ndle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.688: [realtek] Init entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.688: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.689: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.689: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.689: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.690: [realtek] Init completed successfully 287s (process:2087): libfprint-realtek-DEBUG: 17:02:45.690: Init complete! 287s (process:2087): libfprint-device-DEBUG: 17:02:45.690: Device reported open completion 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.690: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-device-DEBUG: 17:02:45.690: Completing action FPI_DEVICE_ACTION_OPEN in idle! 287s (process:2087): libfprint-device-DEBUG: 17:02:45.690: Not updating temperature model, device can run continuously! 287s (process:2087): libfprint-realtek-DEBUG: 17:02:45.690: 121675187: ../libfprint/drivers/realtek/realtek.c:1167 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.690: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.690: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.690: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-realtek-DEBUG: 17:02:45.691: Successfully cleared storage 287s (process:2087): libfprint-device-DEBUG: 17:02:45.691: Device reported deletion completion 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.691: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-device-DEBUG: 17:02:45.691: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 287s (process:2087): libfprint-device-DEBUG: 17:02:45.691: Not updating temperature model, device can run continuously! 287s (process:2087): libfprint-device-DEBUG: 17:02:45.691: Not updating temperature model, device can run continuously! 287s (process:2087): libfprint-realtek-DEBUG: 17:02:45.691: 121676881: ../libfprint/drivers/realtek/realtek.c:1036 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.691: [realtek] Enroll entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.691: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.692: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.692: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.693: [realtek] Enroll entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.693: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.693: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.693: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.693: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.694: [realtek] Enroll entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.694: Device reported finger status change: FP_FINGER_STATUS_NEEDED 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.694: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.694: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.694: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.694: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.695: [realtek] Enroll entering state 3 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.695: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.695: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.695: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.696: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.696: Device reported finger status change: FP_FINGER_STATUS_PRESENT 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.696: [realtek] Enroll entering state 4 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.696: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.696: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.697: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.697: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.697: Device reported finger status change: FP_FINGER_STATUS_NONE 287s (process:2087): libfprint-device-DEBUG: 17:02:45.697: Device reported enroll progress, reported 1 of 8 have been completed 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.700: [realtek] Enroll entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.700: Device reported finger status change: FP_FINGER_STATUS_NEEDED 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.700: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.700: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.700: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.700: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.701: [realtek] Enroll entering state 3 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.701: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.701: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.701: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.702: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.702: Device reported finger status change: FP_FINGER_STATUS_PRESENT 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.702: [realtek] Enroll entering state 4 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.702: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.703: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.703: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.703: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.704: Device reported finger status change: FP_FINGER_STATUS_NONE 287s (process:2087): libfprint-device-DEBUG: 17:02:45.704: Device reported enroll progress, reported 2 of 8 have been completed 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.704: [realtek] Enroll entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.704: Device reported finger status change: FP_FINGER_STATUS_NEEDED 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.704: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.704: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.704: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.704: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.705: [realtek] Enroll entering state 3 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.705: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.705: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.705: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.706: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.706: Device reported finger status change: FP_FINGER_STATUS_PRESENT 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.706: [realtek] Enroll entering state 4 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.706: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.707: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.707: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.707: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.708: Device reported finger status change: FP_FINGER_STATUS_NONE 287s (process:2087): libfprint-device-DEBUG: 17:02:45.708: Device reported enroll progress, reported 3 of 8 have been completed 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.708: [realtek] Enroll entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.708: Device reported finger status change: FP_FINGER_STATUS_NEEDED 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.708: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.708: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.708: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.708: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.709: [realtek] Enroll entering state 3 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.709: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.709: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.709: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.710: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.710: Device reported finger status change: FP_FINGER_STATUS_PRESENT 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.710: [realtek] Enroll entering state 4 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.710: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.710: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.710: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.711: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.711: Device reported finger status change: FP_FINGER_STATUS_NONE 287s (process:2087): libfprint-device-DEBUG: 17:02:45.711: Device reported enroll progress, reported 4 of 8 have been completed 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.711: [realtek] Enroll entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.711: Device reported finger status change: FP_FINGER_STATUS_NEEDED 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.711: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.712: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.712: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.712: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.712: [realtek] Enroll entering state 3 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.712: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.712: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.713: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.713: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.713: Device reported finger status change: FP_FINGER_STATUS_PRESENT 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.713: [realtek] Enroll entering state 4 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.713: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.714: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.714: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.714: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.715: Device reported finger status change: FP_FINGER_STATUS_NONE 287s (process:2087): libfprint-device-DEBUG: 17:02:45.715: Device reported enroll progress, reported 5 of 8 have been completed 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.715: [realtek] Enroll entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.715: Device reported finger status change: FP_FINGER_STATUS_NEEDED 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.715: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.715: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.715: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.715: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.716: [realtek] Enroll entering state 3 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.716: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.716: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.716: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.717: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.717: Device reported finger status change: FP_FINGER_STATUS_PRESENT 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.717: [realtek] Enroll entering state 4 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.717: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.717: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.718: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.718: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.718: Device reported finger status change: FP_FINGER_STATUS_NONE 287s (process:2087): libfprint-device-DEBUG: 17:02:45.718: Device reported enroll progress, reported 6 of 8 have been completed 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.718: [realtek] Enroll entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.718: Device reported finger status change: FP_FINGER_STATUS_NEEDED 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.718: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.719: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.719: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.719: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.719: [realtek] Enroll entering state 3 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.719: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.720: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.720: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.720: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.721: Device reported finger status change: FP_FINGER_STATUS_PRESENT 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.721: [realtek] Enroll entering state 4 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.721: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.721: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.721: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.721: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.722: Device reported finger status change: FP_FINGER_STATUS_NONE 287s (process:2087): libfprint-device-DEBUG: 17:02:45.722: Device reported enroll progress, reported 7 of 8 have been completed 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.722: [realtek] Enroll entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.722: Device reported finger status change: FP_FINGER_STATUS_NEEDED 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.722: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.722: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.722: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.722: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.723: [realtek] Enroll entering state 3 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.723: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.723: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.723: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.724: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.724: Device reported finger status change: FP_FINGER_STATUS_PRESENT 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.724: [realtek] Enroll entering state 4 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.724: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.724: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.725: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.725: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.726: Device reported finger status change: FP_FINGER_STATUS_NONE 287s (process:2087): libfprint-device-DEBUG: 17:02:45.726: Device reported enroll progress, reported 8 of 8 have been completed 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.726: [realtek] Enroll entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.726: Device reported finger status change: FP_FINGER_STATUS_NEEDED 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.726: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.726: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.726: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.726: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.726: [realtek] Enroll entering state 3 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.726: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.727: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.727: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.727: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.728: Device reported finger status change: FP_FINGER_STATUS_PRESENT 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.728: [realtek] Enroll entering state 4 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.728: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.728: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.728: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.729: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.729: Device reported finger status change: FP_FINGER_STATUS_NONE 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.729: [realtek] Enroll entering state 5 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.729: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.729: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.729: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.730: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.730: [realtek] Enroll entering state 6 287s (process:2087): libfprint-realtek-DEBUG: 17:02:45.730: user_id: FP1-00000000-0-00000000-nobody, finger: 0xff 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.730: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.731: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.731: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.731: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.732: [realtek] Enroll completed successfully 287s (process:2087): libfprint-realtek-DEBUG: 17:02:45.732: Enrollment complete! 287s (process:2087): libfprint-device-DEBUG: 17:02:45.732: Device reported enroll completion 287s (process:2087): libfprint-device-DEBUG: 17:02:45.732: Print for finger FP_FINGER_UNKNOWN enrolled 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.732: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-device-DEBUG: 17:02:45.732: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 287s (process:2087): libfprint-device-DEBUG: 17:02:45.732: Not updating temperature model, device can run continuously! 287s (process:2087): libfprint-realtek-DEBUG: 17:02:45.732: 121717264: ../libfprint/drivers/realtek/realtek.c:1179 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.732: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.732: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.733: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-realtek-DEBUG: 17:02:45.733: Query templates complete! 287s (process:2087): libfprint-device-DEBUG: 17:02:45.733: Device reported listing completion 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.733: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-device-DEBUG: 17:02:45.733: Completing action FPI_DEVICE_ACTION_LIST in idle! 287s (process:2087): libfprint-device-DEBUG: 17:02:45.733: Not updating temperature model, device can run continuously! 287s (process:2087): libfprint-device-DEBUG: 17:02:45.733: Not updating temperature model, device can run continuously! 287s (process:2087): libfprint-realtek-DEBUG: 17:02:45.733: 121718742: ../libfprint/drivers/realtek/realtek.c:1009 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.733: [realtek] Verify & Identify entering state 0 287s (process:2087): libfprint-device-DEBUG: 17:02:45.733: Device reported finger status change: FP_FINGER_STATUS_NEEDED 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.733: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.734: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.734: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.734: [realtek] Verify & Identify entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.734: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.734: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.735: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.735: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.735: Device reported finger status change: FP_FINGER_STATUS_PRESENT 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.735: [realtek] Verify & Identify entering state 2 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.735: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.736: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.736: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.736: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.737: Device reported finger status change: FP_FINGER_STATUS_NONE 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.737: [realtek] Verify & Identify entering state 3 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.737: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.737: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.737: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.738: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.738: Device reported verify result 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.738: [realtek] Verify & Identify entering state 4 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.738: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.738: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.738: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.738: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.739: [realtek] Verify & Identify completed successfully 287s (process:2087): libfprint-realtek-DEBUG: 17:02:45.739: Verify complete! 287s (process:2087): libfprint-device-DEBUG: 17:02:45.739: Device reported verify completion 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.739: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-device-DEBUG: 17:02:45.739: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 287s (process:2087): libfprint-device-DEBUG: 17:02:45.739: Not updating temperature model, device can run continuously! 287s (process:2087): libfprint-device-DEBUG: 17:02:45.739: Not updating temperature model, device can run continuously! 287s (process:2087): libfprint-realtek-DEBUG: 17:02:45.739: 121724593: ../libfprint/drivers/realtek/realtek.c:1009 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.739: [realtek] Verify & Identify entering state 0 287s (process:2087): libfprint-device-DEBUG: 17:02:45.739: Device reported finger status change: FP_FINGER_STATUS_NEEDED 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.739: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.740: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.740: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.740: [realtek] Verify & Identify entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.740: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.740: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.741: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.741: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.742: Device reported finger status change: FP_FINGER_STATUS_PRESENT 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.742: [realtek] Verify & Identify entering state 2 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.742: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.742: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.742: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.742: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.743: Device reported finger status change: FP_FINGER_STATUS_NONE 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.743: [realtek] Verify & Identify entering state 3 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.743: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.743: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.743: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.744: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-device-DEBUG: 17:02:45.744: Device reported identify result 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.744: [realtek] Verify & Identify completed successfully 287s (process:2087): libfprint-realtek-DEBUG: 17:02:45.744: Verify complete! 287s (process:2087): libfprint-device-DEBUG: 17:02:45.744: Device reported identify completion 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.744: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-device-DEBUG: 17:02:45.744: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 287s (process:2087): libfprint-device-DEBUG: 17:02:45.744: Not updating temperature model, device can run continuously! 287s (process:2087): libfprint-realtek-DEBUG: 17:02:45.745: 121730151: ../libfprint/drivers/realtek/realtek.c:1148 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.745: [realtek] Delete print entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.745: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.745: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.746: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.746: [realtek] Delete print entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.746: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.746: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.746: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.746: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.747: [realtek] Delete print completed successfully 287s (process:2087): libfprint-realtek-DEBUG: 17:02:45.747: Delete print complete! 287s (process:2087): libfprint-device-DEBUG: 17:02:45.747: Device reported deletion completion 287s (process:2087): libfprint-SSM-DEBUG: 17:02:45.747: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 287s (process:2087): libfprint-device-DEBUG: 17:02:45.747: Completing action FPI_DEVICE_ACTION_DELETE in idle! 287s (process:2087): libfprint-device-DEBUG: 17:02:45.747: Not updating temperature model, device can run continuously! 287s (process:2087): libfprint-realtek-DEBUG: 17:02:45.747: 121732365: ../libfprint/drivers/realtek/realtek.c:1136 287s (process:2087): libfprint-device-DEBUG: 17:02:45.747: Device reported close completion 287s (process:2087): libfprint-device-DEBUG: 17:02:45.748: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 287s (process:2087): libfprint-device-DEBUG: 17:02:45.748: Not updating temperature model, device can run continuously! 287s enrolling 287s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf455123c5880 (FpiDeviceRealtek at 0x215af930)>, 1, None, None, None) 287s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf455123c5880 (FpiDeviceRealtek at 0x215af930)>, 2, None, None, None) 287s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf455123c5880 (FpiDeviceRealtek at 0x215af930)>, 3, None, None, None) 287s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf455123c5880 (FpiDeviceRealtek at 0x215af930)>, 4, None, None, None) 287s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf455123c5880 (FpiDeviceRealtek at 0x215af930)>, 5, None, None, None) 287s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf455123c5880 (FpiDeviceRealtek at 0x215af930)>, 6, None, None, None) 287s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf455123c5880 (FpiDeviceRealtek at 0x215af930)>, 7, None, None, None) 287s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf455123c5880 (FpiDeviceRealtek at 0x215af930)>, 8, None, None, None) 287s enroll done 287s listing 287s listing done 287s verifying 287s verify done 287s async identifying 287s indentification_done: 287s deleting 287s delete done 287s ** (umockdev-run:2083): DEBUG: 17:02:45.760: umockdev.vala:150: Removing test bed /tmp/umockdev.AXUZJ2 287s (umockdev-run:2083): GLib-DEBUG: 17:02:45.764: unsetenv() is not thread-safe and should not be used after threads are created 287s PASS: libfprint-2/driver-realtek.test 287s Running test: libfprint-2/driver-elan.test 287s ** (umockdev-run:2095): DEBUG: 17:02:45.810: umockdev.vala:123: Created udev test bed /tmp/umockdev.AZV5J2 287s ** (umockdev-run:2095): DEBUG: 17:02:45.810: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4 287s ** (umockdev-run:2095): DEBUG: 17:02:45.812: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4 (subsystem usb) 287s ** (umockdev-run:2095): DEBUG: 17:02:45.813: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.AZV5J2/dev/bus/usb/001/094 287s ** (umockdev-run:2095): DEBUG: 17:02:45.814: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-4 287s ** (umockdev-run:2095): DEBUG: 17:02:45.814: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-4 (subsystem usb) 287s ** (umockdev-run:2095): DEBUG: 17:02:45.816: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.AZV5J2/dev/bus/usb/001/083 287s ** (umockdev-run:2095): DEBUG: 17:02:45.816: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 287s ** (umockdev-run:2095): DEBUG: 17:02:45.817: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 287s ** (umockdev-run:2095): DEBUG: 17:02:45.819: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.AZV5J2/dev/bus/usb/001/001 287s ** (umockdev-run:2095): DEBUG: 17:02:45.819: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 287s ** (umockdev-run:2095): DEBUG: 17:02:45.819: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 287s (umockdev-run:2095): GLib-GIO-DEBUG: 17:02:45.821: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 287s (process:2099): libfprint-context-DEBUG: 17:02:45.875: Initializing FpContext (libfprint version 1.94.7+tod1) 287s (process:2099): libfprint-tod-DEBUG: 17:02:45.876: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 287s (process:2099): libfprint-context-DEBUG: 17:02:45.878: No driver found for USB device 17EF:1018 287s (process:2099): libfprint-context-DEBUG: 17:02:45.878: No driver found for USB device 1D6B:0002 287s (process:2099): libfprint-device-DEBUG: 17:02:45.878: Device reported probe completion 287s (process:2099): libfprint-device-DEBUG: 17:02:45.878: Completing action FPI_DEVICE_ACTION_PROBE in idle! 287s (process:2099): libfprint-device-DEBUG: 17:02:45.878: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 287s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find ha(process:2099): libfprint-elan-DEBUG: 17:02:45.882: 121866939: ../libfprint/drivers/elan.c:908 288s (process:2099): libfprint-image_device-DEBUG: 17:02:45.882: Image device open completed 288s (process:2099): libfprint-device-DEBUG: 17:02:45.882: Device reported open completion 288s (process:2099): libfprint-device-DEBUG: 17:02:45.882: Completing action FPI_DEVICE_ACTION_OPEN in idle! 288s (process:2099): libfprint-device-DEBUG: 17:02:45.882: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 288s (process:2099): libfprint-device-DEBUG: 17:02:45.882: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 288s (process:2099): libfprint-image_device-DEBUG: 17:02:45.882: Activating image device 288s (process:2099): libfprint-image_device-DEBUG: 17:02:45.882: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.882: 121867347: ../libfprint/drivers/elan.c:960 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.882: 121867351: ../libfprint/drivers/elan.c:951 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.882: 121867354: ../libfprint/drivers/elan.c:892 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.882: 121867356: ../libfprint/drivers/elan.c:100 288s (process:2099): libfprint-SSM-DEBUG: 17:02:45.882: [elan] ACTIVATE_NUM_STATES entering state 0 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.882: 121867370: ../libfprint/drivers/elan.c:820 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.883: 121868051: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.883: 121868122: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.883: 121868130: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.883: 121868615: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.883: 121868627: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:45.883: [elan] ACTIVATE_NUM_STATES entering state 1 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.883: 121868636: ../libfprint/drivers/elan.c:820 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.883: FW ver 0x0140 288s (process:2099): libfprint-SSM-DEBUG: 17:02:45.883: [elan] ACTIVATE_NUM_STATES entering state 2 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.883: 121868644: ../libfprint/drivers/elan.c:820 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.884: 121868985: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.884: 121868994: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.884: 121868997: ../libfprint/drivers/elan.c:379 288s ndle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s libusb: error [op_handle_events] cannot find handle for fd 9 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.884: 121869341: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.884: 121869351: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:45.884: [elan] ACTIVATE_NUM_STATES entering state 3 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.884: 121869357: ../libfprint/drivers/elan.c:820 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.884: sensor dimensions, WxH: 144x64 288s (process:2099): libfprint-SSM-DEBUG: 17:02:45.884: [elan] ACTIVATE_NUM_STATES entering state 4 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.884: 121869365: ../libfprint/drivers/elan.c:820 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.884: skipping command 0x40 0x2a for this device (for devices 0x1 but device is 0x0) 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.884: 121869371: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:45.884: [elan] ACTIVATE_NUM_STATES completed successfully 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.884: 121869377: ../libfprint/drivers/elan.c:881 288s (process:2099): libfprint-image_device-DEBUG: 17:02:45.884: Image device activation completed 288s (process:2099): libfprint-image_device-DEBUG: 17:02:45.884: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.884: 121869391: ../libfprint/drivers/elan.c:960 288s (process:2099): libfprint-image_device-DEBUG: 17:02:45.884: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.884: 121869399: ../libfprint/drivers/elan.c:960 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.884: 121869402: ../libfprint/drivers/elan.c:792 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.884: 121869405: ../libfprint/drivers/elan.c:100 288s (process:2099): libfprint-SSM-DEBUG: 17:02:45.884: [elan] CALIBRATE_NUM_STATES entering state 0 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.884: 121869411: ../libfprint/drivers/elan.c:691 288s (process:2099): libfprint-device-DEBUG: 17:02:45.884: Device reported finger status change: FP_FINGER_STATUS_NEEDED 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.884: 121869822: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.884: 121869859: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.884: 121869891: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.885: 121870320: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.885: 121870382: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:45.885: [elan] CALIBRATE_NUM_STATES entering state 1 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.885: 121870486: ../libfprint/drivers/elan.c:691 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.885: 121870567: ../libfprint/drivers/elan.c:156 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.885: 121870743: ../libfprint/drivers/elan.c:118 288s (process:2099): libfprint-SSM-DEBUG: 17:02:45.886: [elan] CALIBRATE_NUM_STATES entering state 2 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.886: 121871162: ../libfprint/drivers/elan.c:691 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.886: 121871569: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.886: 121871578: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.886: 121871581: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.887: 121872021: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.887: 121872076: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:45.887: [elan] CALIBRATE_NUM_STATES entering state 3 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.887: 121872087: ../libfprint/drivers/elan.c:691 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.887: 121872090: ../libfprint/drivers/elan.c:634 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.887: calibration mean: 8421, bg mean: 5805, delta: 2616 288s (process:2099): libfprint-SSM-DEBUG: 17:02:45.887: [elan] CALIBRATE_NUM_STATES entering state 4 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.887: 121872102: ../libfprint/drivers/elan.c:691 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.887: 121872539: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.887: 121872549: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.887: 121872551: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.888: 121872923: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.888: 121872932: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:45.888: [elan] CALIBRATE_NUM_STATES entering state 5 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.888: 121872939: ../libfprint/drivers/elan.c:691 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.888: calibration status: 0x01 288s (process:2099): libfprint-SSM-DEBUG: 17:02:45.938: [elan] CALIBRATE_NUM_STATES entering state 6 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.938: 121923055: ../libfprint/drivers/elan.c:691 288s (process:2099): libfprint-SSM-DEBUG: 17:02:45.938: [elan] CALIBRATE_NUM_STATES entering state 4 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.938: 121923069: ../libfprint/drivers/elan.c:691 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.938: 121923477: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.938: 121923488: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.938: 121923491: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.938: 121923889: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.938: 121923898: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:45.938: [elan] CALIBRATE_NUM_STATES entering state 5 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.938: 121923905: ../libfprint/drivers/elan.c:691 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.939: calibration status: 0x01 288s (process:2099): libfprint-device-DEBUG: 17:02:45.983: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 288s (process:2099): libfprint-SSM-DEBUG: 17:02:45.989: [elan] CALIBRATE_NUM_STATES entering state 6 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.989: 121974276: ../libfprint/drivers/elan.c:691 288s (process:2099): libfprint-SSM-DEBUG: 17:02:45.989: [elan] CALIBRATE_NUM_STATES entering state 4 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.989: 121974287: ../libfprint/drivers/elan.c:691 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.989: 121974740: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.989: 121974751: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.989: 121974753: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.990: 121975251: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.990: 121975262: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:45.990: [elan] CALIBRATE_NUM_STATES entering state 5 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.990: 121975269: ../libfprint/drivers/elan.c:691 288s (process:2099): libfprint-elan-DEBUG: 17:02:45.990: calibration status: 0x01 288s Executing: libfprint-2/driver-elan.test 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.040: [elan] CALIBRATE_NUM_STATES entering state 6 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.040: 122025550: ../libfprint/drivers/elan.c:691 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.040: [elan] CALIBRATE_NUM_STATES entering state 4 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.040: 122025853: ../libfprint/drivers/elan.c:691 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.041: 122026404: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.041: 122026469: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.041: 122026559: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.042: 122027068: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.042: 122027079: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.042: [elan] CALIBRATE_NUM_STATES entering state 5 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.042: 122027087: ../libfprint/drivers/elan.c:691 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.042: calibration status: 0x01 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.092: [elan] CALIBRATE_NUM_STATES entering state 6 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.092: 122077281: ../libfprint/drivers/elan.c:691 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.092: [elan] CALIBRATE_NUM_STATES entering state 4 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.092: 122077289: ../libfprint/drivers/elan.c:691 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.092: 122077765: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.092: 122077776: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.092: 122077779: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.093: 122078281: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.093: 122078291: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.093: [elan] CALIBRATE_NUM_STATES entering state 5 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.093: 122078298: ../libfprint/drivers/elan.c:691 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.093: calibration status: 0x01 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.143: [elan] CALIBRATE_NUM_STATES entering state 6 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.143: 122128422: ../libfprint/drivers/elan.c:691 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.143: [elan] CALIBRATE_NUM_STATES entering state 4 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.143: 122128430: ../libfprint/drivers/elan.c:691 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.144: 122128977: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.144: 122129050: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.144: 122129096: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.144: 122129559: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.144: 122129570: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.144: [elan] CALIBRATE_NUM_STATES entering state 5 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.144: 122129577: ../libfprint/drivers/elan.c:691 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.144: calibration status: 0x03 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.144: [elan] CALIBRATE_NUM_STATES entering state 0 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.144: 122129585: ../libfprint/drivers/elan.c:691 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.145: 122129971: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.145: 122129982: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.145: 122129984: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.145: 122130506: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.145: 122130538: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.145: [elan] CALIBRATE_NUM_STATES entering state 1 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.145: 122130546: ../libfprint/drivers/elan.c:691 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.145: 122130548: ../libfprint/drivers/elan.c:156 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.145: 122130551: ../libfprint/drivers/elan.c:118 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.145: [elan] CALIBRATE_NUM_STATES entering state 2 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.145: 122130563: ../libfprint/drivers/elan.c:691 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.146: 122131066: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.146: 122131116: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.146: 122131122: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.146: 122131543: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.146: 122131552: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.146: [elan] CALIBRATE_NUM_STATES entering state 3 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.146: 122131559: ../libfprint/drivers/elan.c:691 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.146: 122131561: ../libfprint/drivers/elan.c:634 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.146: calibration mean: 8339, bg mean: 8146, delta: 193 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.146: [elan] CALIBRATE_NUM_STATES completed successfully 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.146: 122131579: ../libfprint/drivers/elan.c:776 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.146: 122131581: ../libfprint/drivers/elan.c:620 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.146: 122131584: ../libfprint/drivers/elan.c:100 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.146: [elan] CAPTURE_NUM_STATES entering state 0 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.147: 122132050: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.147: 122132078: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.147: 122132085: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.147: skipping read, not expecting anything 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.147: 122132090: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.147: [elan] CAPTURE_NUM_STATES entering state 1 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.147: 122132546: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.147: 122132556: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.147: 122132558: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.148: 122132976: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.148: 122132999: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.148: [elan] CAPTURE_NUM_STATES entering state 2 288s (process:2099): libfprint-device-DEBUG: 17:02:46.148: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 288s (process:2099): libfprint-image_device-DEBUG: 17:02:46.148: Image device reported finger status: on 288s (process:2099): libfprint-image_device-DEBUG: 17:02:46.148: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.148: 122133056: ../libfprint/drivers/elan.c:960 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.148: 122133518: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.148: 122133529: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.148: 122133532: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.149: 122133992: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.149: 122134016: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.149: [elan] CAPTURE_NUM_STATES entering state 3 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.149: 122134027: ../libfprint/drivers/elan.c:203 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.149: 122134029: ../libfprint/drivers/elan.c:118 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.149: [elan] CAPTURE_NUM_STATES entering state 1 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.149: 122134421: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.149: 122134468: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.149: 122134475: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.150: 122134904: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.150: 122134914: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.150: [elan] CAPTURE_NUM_STATES entering state 2 288s (process:2099): libfprint-image_device-DEBUG: 17:02:46.150: Image device reported finger status: on 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.150: 122135293: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.150: 122135362: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.150: 122135378: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.150: 122135805: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.150: 122135816: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.150: [elan] CAPTURE_NUM_STATES entering state 3 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.150: 122135823: ../libfprint/drivers/elan.c:203 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.150: 122135833: ../libfprint/drivers/elan.c:118 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.150: [elan] CAPTURE_NUM_STATES entering state 1 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.151: 122136331: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.151: 122136368: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.151: 122136375: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.151: 122136811: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.151: 122136821: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.151: [elan] CAPTURE_NUM_STATES entering state 2 288s (process:2099): libfprint-image_device-DEBUG: 17:02:46.151: Image device reported finger status: on 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.152: 122137228: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.152: 122137237: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.152: 122137240: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.152: 122137683: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.152: 122137694: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.152: [elan] CAPTURE_NUM_STATES entering state 3 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.152: 122137701: ../libfprint/drivers/elan.c:203 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.152: 122137709: ../libfprint/drivers/elan.c:118 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.152: [elan] CAPTURE_NUM_STATES entering state 1 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.153: 122138166: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.153: 122138175: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.153: 122138178: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.153: 122138619: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.153: 122138647: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.153: [elan] CAPTURE_NUM_STATES entering state 2 288s (process:2099): libfprint-image_device-DEBUG: 17:02:46.153: Image device reported finger status: on 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.154: 122139082: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.154: 122139091: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.154: 122139094: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.154: 122139625: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.154: 122139637: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.154: [elan] CAPTURE_NUM_STATES entering state 3 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.154: 122139644: ../libfprint/drivers/elan.c:203 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.154: 122139652: ../libfprint/drivers/elan.c:118 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.154: [elan] CAPTURE_NUM_STATES entering state 1 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.155: 122140062: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.155: 122140146: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.155: 122140170: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.155: 122140680: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.155: 122140691: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.155: [elan] CAPTURE_NUM_STATES entering state 2 288s (process:2099): libfprint-image_device-DEBUG: 17:02:46.155: Image device reported finger status: on 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.156: 122141159: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.156: 122141170: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.156: 122141172: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.156: 122141585: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.156: 122141615: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.156: [elan] CAPTURE_NUM_STATES entering state 3 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.156: 122141628: ../libfprint/drivers/elan.c:203 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.156: 122141635: ../libfprint/drivers/elan.c:118 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.156: [elan] CAPTURE_NUM_STATES entering state 1 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.157: 122142201: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.157: 122142211: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.157: 122142214: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.157: 122142643: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.157: 122142654: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.157: [elan] CAPTURE_NUM_STATES entering state 2 288s (process:2099): libfprint-image_device-DEBUG: 17:02:46.157: Image device reported finger status: on 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.158: 122143064: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.158: 122143074: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.158: 122143076: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.158: 122143527: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.158: 122143538: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.158: [elan] CAPTURE_NUM_STATES entering state 3 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.158: 122143545: ../libfprint/drivers/elan.c:203 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.158: 122143552: ../libfprint/drivers/elan.c:118 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.158: [elan] CAPTURE_NUM_STATES entering state 1 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.159: 122144029: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.159: 122144129: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.159: 122144148: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.159: 122144630: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.159: 122144665: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.159: [elan] CAPTURE_NUM_STATES entering state 2 288s (process:2099): libfprint-image_device-DEBUG: 17:02:46.159: Image device reported finger status: on 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.160: 122145160: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.160: 122145169: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.160: 122145172: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.160: 122145638: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.160: 122145666: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.160: [elan] CAPTURE_NUM_STATES entering state 3 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.160: 122145676: ../libfprint/drivers/elan.c:203 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.160: 122145683: ../libfprint/drivers/elan.c:118 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.160: [elan] CAPTURE_NUM_STATES entering state 1 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.161: 122146184: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.161: 122146194: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.161: 122146197: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.161: 122146618: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.161: 122146628: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.161: [elan] CAPTURE_NUM_STATES entering state 2 288s (process:2099): libfprint-image_device-DEBUG: 17:02:46.161: Image device reported finger status: on 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.162: 122147068: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.162: 122147079: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.162: 122147081: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.162: 122147518: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.162: 122147530: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.162: [elan] CAPTURE_NUM_STATES entering state 3 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.162: 122147536: ../libfprint/drivers/elan.c:203 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.162: 122147544: ../libfprint/drivers/elan.c:118 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.162: [elan] CAPTURE_NUM_STATES entering state 1 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.163: 122147997: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.163: 122148017: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.163: 122148020: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.163: 122148507: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.163: 122148518: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.163: [elan] CAPTURE_NUM_STATES entering state 2 288s (process:2099): libfprint-image_device-DEBUG: 17:02:46.163: Image device reported finger status: on 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.164: 122148977: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.164: 122148987: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.164: 122148990: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.164: 122149435: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.164: 122149447: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.164: [elan] CAPTURE_NUM_STATES entering state 3 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.164: 122149453: ../libfprint/drivers/elan.c:203 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.164: 122149471: ../libfprint/drivers/elan.c:118 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.164: [elan] CAPTURE_NUM_STATES entering state 1 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.165: 122149961: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.165: 122149972: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.165: 122149975: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.165: 122150432: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.165: 122150443: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.165: [elan] CAPTURE_NUM_STATES entering state 2 288s (process:2099): libfprint-image_device-DEBUG: 17:02:46.165: Image device reported finger status: on 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.165: 122150856: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.165: 122150866: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.165: 122150869: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.166: 122151400: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.166: 122151413: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.166: [elan] CAPTURE_NUM_STATES entering state 3 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.166: 122151420: ../libfprint/drivers/elan.c:203 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.166: 122151428: ../libfprint/drivers/elan.c:118 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.166: [elan] CAPTURE_NUM_STATES entering state 1 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.167: 122151911: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.167: 122151921: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.167: 122151924: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.167: 122152379: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.167: 122152389: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.167: [elan] CAPTURE_NUM_STATES entering state 2 288s (process:2099): libfprint-image_device-DEBUG: 17:02:46.167: Image device reported finger status: on 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.167: 122152808: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.167: 122152817: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.167: 122152820: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.168: 122153293: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.168: 122153323: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.168: [elan] CAPTURE_NUM_STATES entering state 3 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.168: 122153334: ../libfprint/drivers/elan.c:203 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.168: 122153342: ../libfprint/drivers/elan.c:118 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.168: [elan] CAPTURE_NUM_STATES entering state 1 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.168: 122153841: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.168: 122153863: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.168: 122153869: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.169: 122154281: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.169: 122154290: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.169: [elan] CAPTURE_NUM_STATES entering state 2 288s (process:2099): libfprint-image_device-DEBUG: 17:02:46.169: Image device reported finger status: on 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.169: 122154737: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.169: 122154746: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.169: 122154749: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.170: 122155224: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.170: 122155235: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.170: [elan] CAPTURE_NUM_STATES entering state 3 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.170: 122155242: ../libfprint/drivers/elan.c:203 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.170: 122155250: ../libfprint/drivers/elan.c:118 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.170: [elan] CAPTURE_NUM_STATES entering state 1 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.170: 122155736: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.170: 122155746: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.170: 122155749: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.171: 122156113: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.171: 122156124: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.171: [elan] CAPTURE_NUM_STATES entering state 2 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.171: [elan] CAPTURE_NUM_STATES completed successfully 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.171: 122156137: ../libfprint/drivers/elan.c:586 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.171: 122156140: ../libfprint/drivers/elan.c:315 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.171: 122156146: ../libfprint/drivers/elan.c:272 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.171: 122156895: ../libfprint/drivers/elan.c:272 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.172: 122157642: ../libfprint/drivers/elan.c:272 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.173: 122158371: ../libfprint/drivers/elan.c:272 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.174: 122159116: ../libfprint/drivers/elan.c:272 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.174: 122159851: ../libfprint/drivers/elan.c:272 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.176: 122161631: ../libfprint/drivers/elan.c:272 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.178: 122163642: ../libfprint/drivers/elan.c:272 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.180: 122165812: ../libfprint/drivers/elan.c:272 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.183: 122167945: ../libfprint/drivers/elan.c:272 288s (process:2099): libfprint-assembling-DEBUG: 17:02:46.496: calc delta completed in 0.311714 secs 288s (process:2099): libfprint-assembling-DEBUG: 17:02:46.802: calc delta completed in 0.304804 secs 288s (process:2099): libfprint-assembling-DEBUG: 17:02:46.802: errors: 233151 rev: 207411 288s (process:2099): libfprint-assembling-DEBUG: 17:02:46.802: height is -185 288s (process:2099): libfprint-image_device-DEBUG: 17:02:46.803: Image device captured an image 288s (process:2099): libfprint-image_device-DEBUG: 17:02:46.803: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.803: 122788870: ../libfprint/drivers/elan.c:960 288s (process:2099): libfprint-device-DEBUG: 17:02:46.803: Device reported finger status change: FP_FINGER_STATUS_PRESENT 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.803: 122788883: ../libfprint/drivers/elan.c:507 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.803: 122788885: ../libfprint/drivers/elan.c:100 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.803: [elan] STOP_CAPTURE_NUM_STATES entering state 0 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.803: 122788904: ../libfprint/drivers/elan.c:466 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.804: 122789319: ../libfprint/drivers/elan.c:346 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.804: 122789330: ../libfprint/drivers/elan.c:366 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.804: 122789333: ../libfprint/drivers/elan.c:379 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.804: skipping read, not expecting anything 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.804: 122789338: ../libfprint/drivers/elan.c:335 288s (process:2099): libfprint-SSM-DEBUG: 17:02:46.804: [elan] STOP_CAPTURE_NUM_STATES completed successfully 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.804: 122789345: ../libfprint/drivers/elan.c:483 288s (process:2099): libfprint-device-DEBUG: 17:02:46.804: Device reported finger status change: FP_FINGER_STATUS_NONE 288s (process:2099): libfprint-image_device-DEBUG: 17:02:46.804: Image device reported finger status: off 288s (process:2099): libfprint-image_device-DEBUG: 17:02:46.804: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.804: 122789361: ../libfprint/drivers/elan.c:960 288s (process:2099): libfprint-image_device-DEBUG: 17:02:46.804: Deactivating image device 288s (process:2099): libfprint-image_device-DEBUG: 17:02:46.804: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.804: 122789371: ../libfprint/drivers/elan.c:960 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.804: 122789373: ../libfprint/drivers/elan.c:975 288s (process:2099): libfprint-image_device-DEBUG: 17:02:46.804: Image device deactivation completed 288s (process:2099): libfprint-image_device-DEBUG: 17:02:46.804: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.804: 122789385: ../libfprint/drivers/elan.c:960 288s (process:2099): libfprint-image-DEBUG: 17:02:46.834: Minutiae scan completed in 0.029532 secs 288s (process:2099): libfprint-device-DEBUG: 17:02:46.834: Device reported capture completion 288s (process:2099): libfprint-device-DEBUG: 17:02:46.835: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 288s (process:2099): libfprint-device-DEBUG: 17:02:46.835: Updated temperature model after 0.85 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.835: 122820587: ../libfprint/drivers/elan.c:939 288s (process:2099): libfprint-elan-DEBUG: 17:02:46.835: 122820750: ../libfprint/drivers/elan.c:100 288s (process:2099): libfprint-image_device-DEBUG: 17:02:46.836: Image device close completed 288s (process:2099): libfprint-device-DEBUG: 17:02:46.836: Device reported close completion 288s (process:2099): libfprint-device-DEBUG: 17:02:46.836: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 288s (process:2099): libfprint-device-DEBUG: 17:02:46.836: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 288s ** (umockdev-run:2095): DEBUG: 17:02:46.907: umockdev.vala:150: Removing test bed /tmp/umockdev.AZV5J2 288s (umockdev-run:2095): GLib-DEBUG: 17:02:46.912: unsetenv() is not thread-safe and should not be used after threads are created 288s Comparing PNGs /tmp/libfprint-umockdev-test-8ph_0rzr/capture.png and /usr/share/installed-tests/libfprint-2/elan/capture.png 288s PASS: libfprint-2/driver-elan.test 288s Running test: libfprint-2/driver-fpcmoc.test 289s ** (umockdev-run:2108): DEBUG: 17:02:46.974: umockdev.vala:123: Created udev test bed /tmp/umockdev.AES3J2 289s ** (umockdev-run:2108): DEBUG: 17:02:46.975: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-1 289s ** (umockdev-run:2108): DEBUG: 17:02:46.976: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-1 (subsystem usb) 289s ** (umockdev-run:2108): DEBUG: 17:02:46.978: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.AES3J2/dev/bus/usb/001/019 289s ** (umockdev-run:2108): DEBUG: 17:02:46.978: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 289s ** (umockdev-run:2108): DEBUG: 17:02:46.979: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 289s ** (umockdev-run:2108): DEBUG: 17:02:46.981: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.AES3J2/dev/bus/usb/001/001 289s ** (umockdev-run:2108): DEBUG: 17:02:46.981: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 289s ** (umockdev-run:2108): DEBUG: 17:02:46.982: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 289s (process:2112): libfprint-context-DEBUG: 17:02:47.029: Initializing FpContext (libfprint version 1.94.7+tod1) 289s (process:2112): libfprint-tod-DEBUG: 17:02:47.029: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 289s (process:2112): libfprint-DEBUG: 17:02:47.030: fpi_device_fpcmoc_init enter --> 289s (process:2112): libfprint-DEBUG: 17:02:47.031: 123015911: ../libfprint/drivers/fpcmoc/fpc.c:1854 289s (process:2112): libfprint-context-DEBUG: 17:02:47.031: No driver found for USB device 1D6B:0002 289s (process:2112): libfprint-DEBUG: 17:02:47.031: fpc_dev_probe enter --> 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s (process:2112): libfprint-DEBUG: 17:02:47.035: Device name: FPC L:0001 FW:127010 289s (process:2112): libfprint-device-DEBUG: 17:02:47.035: Device reported probe completion 289s (process:2112): libfprint-device-DEBUG: 17:02:47.035: Completing action FPI_DEVICE_ACTION_PROBE in idle! 289s (process:2112): libfprint-device-DEBUG: 17:02:47.035: Not updating temperature model, device can run continuously! 289s (process:2112): libfprint-DEBUG: 17:02:47.036: fpc_dev_open enter --> 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.036: [fpcmoc] FP_INIT_NUM_STATES entering state 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.036: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.036: fpc_send_ctrl_cmd CMD: 0x1, value: 0x1, index: 0 type: 2 289s (process:2112): libfprint-DEBUG: 17:02:47.037: fpc_cmd_receive_cb current ssm request: 1 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.037: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.037: fpc_cmd_receive_cb current ssm request: 1 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.037: fpc_cmd_receive_cb recv evt data length: 38 289s (process:2112): libfprint-DEBUG: 17:02:47.037: fpc_evt_cb INIT: status=0, Sensor = 1523, HWID = 0x1711, WxH = 96 x 96 289s (process:2112): libfprint-DEBUG: 17:02:47.037: fpc_evt_cb INIT: FW version: 1.27.0.10 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.037: [fpcmoc] FP_INIT_NUM_STATES entering state 1 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.037: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.037: fpc_send_ctrl_cmd CMD: 0x60, value: 0x0, index: 0 type: 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.038: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.038: fpc_cmd_receive_cb current ssm request: 96 state: 0 289s (process:2112): libfprint-DEBUG: 17:02:47.038: fpc_init_load_db_cb got dbid size: 16 289s (process:2112): libfprint-DEBUG: 17:02:47.038: fpc_init_load_db_cb dbid: 0xa981b581-adfc-e643-a0d0-88c2138092f7 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.038: [fpcmoc] FP_INIT_NUM_STATES completed successfully 289s (process:2112): libfprint-device-DEBUG: 17:02:47.038: Device reported open completion 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.038: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-device-DEBUG: 17:02:47.038: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s (process:2112): libfprint-device-DEBUG: 17:02:47.038: Not updating temperature model, device can run continuously! 289s (process:2112): libfprint-DEBUG: 17:02:47.038: fpc_dev_clear_storage enter --> 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.038: [fpcmoc] Clear storage entering state 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.038: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.038: fpc_send_ctrl_cmd CMD: 0x62, value: 0x0, index: 0 type: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.038: fpc_cmd_receive_cb current ssm request: 98 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.038: [fpcmoc] Clear storage entering state 1 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.038: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.038: fpc_send_ctrl_cmd CMD: 0x60, value: 0x1, index: 0 type: 1 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.039: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.039: fpc_cmd_receive_cb current ssm request: 96 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.039: [fpcmoc] Clear storage completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.039: Clear Storage complete! 289s (process:2112): libfprint-device-DEBUG: 17:02:47.039: Device reported deletion completion 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.039: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-device-DEBUG: 17:02:47.039: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 289s (process:2112): libfprint-device-DEBUG: 17:02:47.039: Not updating temperature model, device can run continuously! 289s (process:2112): libfprint-device-DEBUG: 17:02:47.039: Not updating temperature model, device can run continuously! 289s (process:2112): libfprint-DEBUG: 17:02:47.039: fpc_dev_enroll enter --> 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.039: [fpcmoc] enroll entering state 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.039: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.039: fpc_send_ctrl_cmd CMD: 0x70, value: 0x0, index: 0 type: 2 289s (process:2112): libfprint-DEBUG: 17:02:47.040: fpc_cmd_receive_cb current ssm request: 112 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.040: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.040: fpc_cmd_receive_cb current ssm request: 112 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.040: fpc_cmd_receive_cb recv evt data length: 790 289s (process:2112): libfprint-DEBUG: 17:02:47.040: fpc_evt_cb Enum Fids: status = 0, NumFids = 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.040: [fpcmoc] enroll entering state 1 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.040: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.040: fpc_send_ctrl_cmd CMD: 0x67, value: 0x0, index: 0 type: 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.041: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.041: fpc_cmd_receive_cb current ssm request: 103 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.041: [fpcmoc] enroll entering state 2 289s (process:2112): libfprint-device-DEBUG: 17:02:47.041: Device reported finger status change: FP_FINGER_STATUS_NEEDED 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.041: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.041: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.041: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.041: fpc_cmd_receive_cb current ssm request: 2 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.041: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.042: fpc_cmd_receive_cb current ssm request: 2 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.042: fpc_cmd_receive_cb recv evt data length: 12 289s (process:2112): libfprint-DEBUG: 17:02:47.042: fpc_evt_cb Got finger down event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.042: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.042: [fpcmoc] enroll entering state 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.042: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.042: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.042: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.042: fpc_cmd_receive_cb current ssm request: 9 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.042: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.043: fpc_cmd_receive_cb current ssm request: 9 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.043: fpc_cmd_receive_cb recv evt data length: 24 289s (process:2112): libfprint-DEBUG: 17:02:47.043: fpc_evt_cb Got capture event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.043: Device reported finger status change: FP_FINGER_STATUS_NEEDED 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.043: [fpcmoc] enroll entering state 4 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.043: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.043: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.043: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.043: fpc_cmd_receive_cb current ssm request: 104 state: 0 289s (process:2112): libfprint-DEBUG: 17:02:47.043: Enrol Update status: 1, remaining: 11 289s (process:2112): libfprint-device-DEBUG: 17:02:47.043: Device reported enroll progress, reported 1 of 25 have been completed 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.043: [fpcmoc] enroll entering state 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.043: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.043: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.044: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.044: fpc_cmd_receive_cb current ssm request: 2 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.044: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.044: fpc_cmd_receive_cb current ssm request: 2 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.044: fpc_cmd_receive_cb recv evt data length: 12 289s (process:2112): libfprint-DEBUG: 17:02:47.044: fpc_evt_cb Got finger down event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.044: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.044: [fpcmoc] enroll entering state 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.044: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.044: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.045: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.045: fpc_cmd_receive_cb current ssm request: 9 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.045: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.045: fpc_cmd_receive_cb current ssm request: 9 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.045: fpc_cmd_receive_cb recv evt data length: 24 289s (process:2112): libfprint-DEBUG: 17:02:47.045: fpc_evt_cb Got capture event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.045: Device reported finger status change: FP_FINGER_STATUS_NEEDED 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.045: [fpcmoc] enroll entering state 4 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.045: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.045: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.046: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.046: fpc_cmd_receive_cb current ssm request: 104 state: 0 289s (process:2112): libfprint-DEBUG: 17:02:47.046: Enrol Update status: 1, remaining: 10 289s (process:2112): libfprint-device-DEBUG: 17:02:47.046: Device reported enroll progress, reported 2 of 25 have been completed 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.046: [fpcmoc] enroll entering state 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.046: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.046: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.046: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.046: fpc_cmd_receive_cb current ssm request: 2 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.046: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.047: fpc_cmd_receive_cb current ssm request: 2 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.047: fpc_cmd_receive_cb recv evt data length: 12 289s (process:2112): libfprint-DEBUG: 17:02:47.047: fpc_evt_cb Got finger down event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.047: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.047: [fpcmoc] enroll entering state 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.047: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.047: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.047: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.047: fpc_cmd_receive_cb current ssm request: 9 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.047: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.048: fpc_cmd_receive_cb current ssm request: 9 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.048: fpc_cmd_receive_cb recv evt data length: 24 289s (process:2112): libfprint-DEBUG: 17:02:47.048: fpc_evt_cb Got capture event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.048: Device reported finger status change: FP_FINGER_STATUS_NEEDED 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.048: [fpcmoc] enroll entering state 4 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.048: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.048: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.048: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.048: fpc_cmd_receive_cb current ssm request: 104 state: 0 289s (process:2112): libfprint-DEBUG: 17:02:47.048: Enrol Update status: 1, remaining: 9 289s (process:2112): libfprint-device-DEBUG: 17:02:47.048: Device reported enroll progress, reported 3 of 25 have been completed 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.049: [fpcmoc] enroll entering state 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.049: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.049: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.049: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.049: fpc_cmd_receive_cb current ssm request: 2 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.049: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.049: fpc_cmd_receive_cb current ssm request: 2 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.049: fpc_cmd_receive_cb recv evt data length: 12 289s (process:2112): libfprint-DEBUG: 17:02:47.049: fpc_evt_cb Got finger down event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.049: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.049: [fpcmoc] enroll entering state 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.049: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.049: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.050: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.050: fpc_cmd_receive_cb current ssm request: 9 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.050: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.050: fpc_cmd_receive_cb current ssm request: 9 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.050: fpc_cmd_receive_cb recv evt data length: 24 289s (process:2112): libfprint-DEBUG: 17:02:47.050: fpc_evt_cb Got capture event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.050: Device reported finger status change: FP_FINGER_STATUS_NEEDED 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.050: [fpcmoc] enroll entering state 4 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.050: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.050: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.051: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.051: fpc_cmd_receive_cb current ssm request: 104 state: 0 289s (process:2112): libfprint-DEBUG: 17:02:47.051: Enrol Update status: 1, remaining: 8 289s (process:2112): libfprint-device-DEBUG: 17:02:47.051: Device reported enroll progress, reported 4 of 25 have been completed 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.051: [fpcmoc] enroll entering state 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.051: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.051: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.051: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.051: fpc_cmd_receive_cb current ssm request: 2 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.051: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.052: fpc_cmd_receive_cb current ssm request: 2 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.052: fpc_cmd_receive_cb recv evt data length: 12 289s (process:2112): libfprint-DEBUG: 17:02:47.052: fpc_evt_cb Got finger down event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.052: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.052: [fpcmoc] enroll entering state 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.052: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.052: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.052: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.052: fpc_cmd_receive_cb current ssm request: 9 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.052: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.053: fpc_cmd_receive_cb current ssm request: 9 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.053: fpc_cmd_receive_cb recv evt data length: 24 289s (process:2112): libfprint-DEBUG: 17:02:47.053: fpc_evt_cb Got capture event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.053: Device reported finger status change: FP_FINGER_STATUS_NEEDED 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.053: [fpcmoc] enroll entering state 4 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.053: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.053: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.053: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.053: fpc_cmd_receive_cb current ssm request: 104 state: 0 289s (process:2112): libfprint-DEBUG: 17:02:47.053: Enrol Update status: 1, remaining: 7 289s (process:2112): libfprint-device-DEBUG: 17:02:47.053: Device reported enroll progress, reported 5 of 25 have been completed 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.053: [fpcmoc] enroll entering state 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.053: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.053: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.054: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.054: fpc_cmd_receive_cb current ssm request: 2 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.054: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.054: fpc_cmd_receive_cb current ssm request: 2 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.054: fpc_cmd_receive_cb recv evt data length: 12 289s (process:2112): libfprint-DEBUG: 17:02:47.054: fpc_evt_cb Got finger down event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.054: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.054: [fpcmoc] enroll entering state 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.054: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.054: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.055: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.055: fpc_cmd_receive_cb current ssm request: 9 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.055: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.055: fpc_cmd_receive_cb current ssm request: 9 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.055: fpc_cmd_receive_cb recv evt data length: 24 289s (process:2112): libfprint-DEBUG: 17:02:47.055: fpc_evt_cb Got capture event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.055: Device reported finger status change: FP_FINGER_STATUS_NEEDED 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.055: [fpcmoc] enroll entering state 4 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.055: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.055: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.056: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.056: fpc_cmd_receive_cb current ssm request: 104 state: 0 289s (process:2112): libfprint-DEBUG: 17:02:47.056: Enrol Update status: 5, remaining: 7 289s (process:2112): libfprint-DEBUG: 17:02:47.056: Sample overlapping ratio is too High 289s (process:2112): libfprint-device-DEBUG: 17:02:47.056: Device reported enroll progress, reported 5 of 25 have been completed 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.056: [fpcmoc] enroll entering state 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.056: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.056: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.056: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.056: fpc_cmd_receive_cb current ssm request: 2 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.056: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.057: fpc_cmd_receive_cb current ssm request: 2 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.057: fpc_cmd_receive_cb recv evt data length: 12 289s (process:2112): libfprint-DEBUG: 17:02:47.057: fpc_evt_cb Got finger down event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.057: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.057: [fpcmoc] enroll entering state 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.057: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.057: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.057: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.057: fpc_cmd_receive_cb current ssm request: 9 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.057: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.058: fpc_cmd_receive_cb current ssm request: 9 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.058: fpc_cmd_receive_cb recv evt data length: 24 289s (process:2112): libfprint-DEBUG: 17:02:47.058: fpc_evt_cb Got capture event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.058: Device reported finger status change: FP_FINGER_STATUS_NEEDED 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.058: [fpcmoc] enroll entering state 4 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.058: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.058: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.058: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.058: fpc_cmd_receive_cb current ssm request: 104 state: 0 289s (process:2112): libfprint-DEBUG: 17:02:47.058: Enrol Update status: 1, remaining: 6 289s (process:2112): libfprint-device-DEBUG: 17:02:47.058: Device reported enroll progress, reported 6 of 25 have been completed 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.058: [fpcmoc] enroll entering state 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.058: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.058: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.058: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.059: fpc_cmd_receive_cb current ssm request: 2 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.059: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.059: fpc_cmd_receive_cb current ssm request: 2 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.059: fpc_cmd_receive_cb recv evt data length: 12 289s (process:2112): libfprint-DEBUG: 17:02:47.059: fpc_evt_cb Got finger down event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.059: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.059: [fpcmoc] enroll entering state 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.059: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.059: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.059: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.059: fpc_cmd_receive_cb current ssm request: 9 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.059: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.060: fpc_cmd_receive_cb current ssm request: 9 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.060: fpc_cmd_receive_cb recv evt data length: 24 289s (process:2112): libfprint-DEBUG: 17:02:47.060: fpc_evt_cb Got capture event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.060: Device reported finger status change: FP_FINGER_STATUS_NEEDED 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.060: [fpcmoc] enroll entering state 4 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.060: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.060: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.060: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.060: fpc_cmd_receive_cb current ssm request: 104 state: 0 289s (process:2112): libfprint-DEBUG: 17:02:47.060: Enrol Update status: 1, remaining: 5 289s (process:2112): libfprint-device-DEBUG: 17:02:47.060: Device reported enroll progress, reported 7 of 25 have been completed 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.060: [fpcmoc] enroll entering state 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.060: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.060: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.061: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.061: fpc_cmd_receive_cb current ssm request: 2 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.061: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.061: fpc_cmd_receive_cb current ssm request: 2 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.061: fpc_cmd_receive_cb recv evt data length: 12 289s (process:2112): libfprint-DEBUG: 17:02:47.061: fpc_evt_cb Got finger down event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.061: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.061: [fpcmoc] enroll entering state 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.061: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.061: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.062: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.062: fpc_cmd_receive_cb current ssm request: 9 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.062: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.062: fpc_cmd_receive_cb current ssm request: 9 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.062: fpc_cmd_receive_cb recv evt data length: 24 289s (process:2112): libfprint-DEBUG: 17:02:47.062: fpc_evt_cb Got capture event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.062: Device reported finger status change: FP_FINGER_STATUS_NEEDED 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.062: [fpcmoc] enroll entering state 4 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.062: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.062: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.062: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.063: fpc_cmd_receive_cb current ssm request: 104 state: 0 289s (process:2112): libfprint-DEBUG: 17:02:47.063: Enrol Update status: 5, remaining: 5 289s (process:2112): libfprint-DEBUG: 17:02:47.063: Sample overlapping ratio is too High 289s (process:2112): libfprint-device-DEBUG: 17:02:47.063: Device reported enroll progress, reported 7 of 25 have been completed 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.063: [fpcmoc] enroll entering state 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.063: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.063: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.063: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.063: fpc_cmd_receive_cb current ssm request: 2 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.063: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.064: fpc_cmd_receive_cb current ssm request: 2 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.064: fpc_cmd_receive_cb recv evt data length: 12 289s (process:2112): libfprint-DEBUG: 17:02:47.064: fpc_evt_cb Got finger down event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.064: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.064: [fpcmoc] enroll entering state 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.064: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.064: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.064: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.064: fpc_cmd_receive_cb current ssm request: 9 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.064: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.064: fpc_cmd_receive_cb current ssm request: 9 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.064: fpc_cmd_receive_cb recv evt data length: 24 289s (process:2112): libfprint-DEBUG: 17:02:47.064: fpc_evt_cb Got capture event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.065: [fpcmoc] enroll entering state 4 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.065: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.065: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.065: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.065: fpc_cmd_receive_cb current ssm request: 104 state: 0 289s (process:2112): libfprint-DEBUG: 17:02:47.065: Enrol Update status: 1, remaining: 4 289s (process:2112): libfprint-device-DEBUG: 17:02:47.065: Device reported enroll progress, reported 8 of 25 have been completed 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.065: [fpcmoc] enroll entering state 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.065: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.065: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.065: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.066: fpc_cmd_receive_cb current ssm request: 2 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.066: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.066: fpc_cmd_receive_cb current ssm request: 2 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.066: fpc_cmd_receive_cb recv evt data length: 12 289s (process:2112): libfprint-DEBUG: 17:02:47.066: fpc_evt_cb Got finger down event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.066: [fpcmoc] enroll entering state 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.066: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.066: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.066: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.066: fpc_cmd_receive_cb current ssm request: 9 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.066: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.067: fpc_cmd_receive_cb current ssm request: 9 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.067: fpc_cmd_receive_cb recv evt data length: 24 289s (process:2112): libfprint-DEBUG: 17:02:47.067: fpc_evt_cb Got capture event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.067: [fpcmoc] enroll entering state 4 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.067: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.067: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.067: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.067: fpc_cmd_receive_cb current ssm request: 104 state: 0 289s (process:2112): libfprint-DEBUG: 17:02:47.067: Enrol Update status: 1, remaining: 3 289s (process:2112): libfprint-device-DEBUG: 17:02:47.067: Device reported enroll progress, reported 9 of 25 have been completed 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.067: [fpcmoc] enroll entering state 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.067: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.067: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.068: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.068: fpc_cmd_receive_cb current ssm request: 2 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.068: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.068: fpc_cmd_receive_cb current ssm request: 2 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.068: fpc_cmd_receive_cb recv evt data length: 12 289s (process:2112): libfprint-DEBUG: 17:02:47.068: fpc_evt_cb Got finger down event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.068: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.068: [fpcmoc] enroll entering state 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.069: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.069: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.069: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.069: fpc_cmd_receive_cb current ssm request: 9 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.069: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.069: fpc_cmd_receive_cb current ssm request: 9 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.069: fpc_cmd_receive_cb recv evt data length: 24 289s (process:2112): libfprint-DEBUG: 17:02:47.069: fpc_evt_cb Got capture event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.069: Device reported finger status change: FP_FINGER_STATUS_NEEDED 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.069: [fpcmoc] enroll entering state 4 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.069: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.069: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.070: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.070: fpc_cmd_receive_cb current ssm request: 104 state: 0 289s (process:2112): libfprint-DEBUG: 17:02:47.070: Enrol Update status: 1, remaining: 2 289s (process:2112): libfprint-device-DEBUG: 17:02:47.070: Device reported enroll progress, reported 10 of 25 have been completed 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.070: [fpcmoc] enroll entering state 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.070: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.070: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.070: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.071: fpc_cmd_receive_cb current ssm request: 2 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.071: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.071: fpc_cmd_receive_cb current ssm request: 2 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.071: fpc_cmd_receive_cb recv evt data length: 12 289s (process:2112): libfprint-DEBUG: 17:02:47.071: fpc_evt_cb Got finger down event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.071: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.071: [fpcmoc] enroll entering state 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.071: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.071: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.071: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.071: fpc_cmd_receive_cb current ssm request: 9 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.071: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.072: fpc_cmd_receive_cb current ssm request: 9 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.072: fpc_cmd_receive_cb recv evt data length: 24 289s (process:2112): libfprint-DEBUG: 17:02:47.072: fpc_evt_cb Got capture event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.072: Device reported finger status change: FP_FINGER_STATUS_NEEDED 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.072: [fpcmoc] enroll entering state 4 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.072: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.072: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.072: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.072: fpc_cmd_receive_cb current ssm request: 104 state: 0 289s (process:2112): libfprint-DEBUG: 17:02:47.072: Enrol Update status: 5, remaining: 2 289s (process:2112): libfprint-DEBUG: 17:02:47.072: Sample overlapping ratio is too High 289s (process:2112): libfprint-device-DEBUG: 17:02:47.072: Device reported enroll progress, reported 10 of 25 have been completed 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.072: [fpcmoc] enroll entering state 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.072: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.072: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.073: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.073: fpc_cmd_receive_cb current ssm request: 2 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.073: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.073: fpc_cmd_receive_cb current ssm request: 2 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.073: fpc_cmd_receive_cb recv evt data length: 12 289s (process:2112): libfprint-DEBUG: 17:02:47.073: fpc_evt_cb Got finger down event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.073: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.073: [fpcmoc] enroll entering state 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.073: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.073: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.074: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.074: fpc_cmd_receive_cb current ssm request: 9 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.074: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.074: fpc_cmd_receive_cb current ssm request: 9 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.074: fpc_cmd_receive_cb recv evt data length: 24 289s (process:2112): libfprint-DEBUG: 17:02:47.074: fpc_evt_cb Got capture event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.074: Device reported finger status change: FP_FINGER_STATUS_NEEDED 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.074: [fpcmoc] enroll entering state 4 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.074: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.074: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.075: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.075: fpc_cmd_receive_cb current ssm request: 104 state: 0 289s (process:2112): libfprint-DEBUG: 17:02:47.075: Enrol Update status: 1, remaining: 1 289s (process:2112): libfprint-device-DEBUG: 17:02:47.075: Device reported enroll progress, reported 11 of 25 have been completed 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.075: [fpcmoc] enroll entering state 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.075: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.075: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.075: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.075: fpc_cmd_receive_cb current ssm request: 2 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.075: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.076: fpc_cmd_receive_cb current ssm request: 2 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.076: fpc_cmd_receive_cb recv evt data length: 12 289s (process:2112): libfprint-DEBUG: 17:02:47.076: fpc_evt_cb Got finger down event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.076: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.076: [fpcmoc] enroll entering state 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.076: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.076: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.076: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.076: fpc_cmd_receive_cb current ssm request: 9 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.076: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.077: fpc_cmd_receive_cb current ssm request: 9 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.077: fpc_cmd_receive_cb recv evt data length: 24 289s (process:2112): libfprint-DEBUG: 17:02:47.077: fpc_evt_cb Got capture event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.077: Device reported finger status change: FP_FINGER_STATUS_NEEDED 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.077: [fpcmoc] enroll entering state 4 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.077: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.077: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.077: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.077: fpc_cmd_receive_cb current ssm request: 104 state: 0 289s (process:2112): libfprint-DEBUG: 17:02:47.077: Enrol Update status: 0, remaining: 0 289s (process:2112): libfprint-device-DEBUG: 17:02:47.077: Device reported enroll progress, reported 12 of 25 have been completed 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.077: [fpcmoc] enroll entering state 5 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.077: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.077: fpc_send_ctrl_cmd CMD: 0x69, value: 0x0, index: 0 type: 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.078: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.078: fpc_cmd_receive_cb current ssm request: 105 state: 0 289s (process:2112): libfprint-DEBUG: 17:02:47.078: Enrol End status: 0, fid: 0x0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.078: [fpcmoc] enroll entering state 6 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.078: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.078: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.078: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.078: fpc_cmd_receive_cb current ssm request: 107 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.078: [fpcmoc] enroll entering state 7 289s (process:2112): libfprint-DEBUG: 17:02:47.078: user_id: FP1-00000000-0-00000000-nobody, finger: 0xf5 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.078: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.078: fpc_send_ctrl_cmd CMD: 0x6a, value: 0x0, index: 0 type: 1 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.079: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.079: fpc_cmd_receive_cb current ssm request: 106 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.079: [fpcmoc] enroll entering state 8 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.079: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.079: fpc_send_ctrl_cmd CMD: 0x61, value: 0x0, index: 0 type: 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.079: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.079: fpc_cmd_receive_cb current ssm request: 97 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.079: [fpcmoc] enroll entering state 9 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.079: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.079: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.080: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.080: fpc_cmd_receive_cb current ssm request: 3 state: 0 289s (process:2112): libfprint-DEBUG: 17:02:47.080: fpc_do_abort_cb Do abort for reasons 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.080: [fpcmoc] enroll entering state 10 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.080: [fpcmoc] enroll completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.080: Enrollment complete! 289s (process:2112): libfprint-device-DEBUG: 17:02:47.080: Device reported enroll completion 289s (process:2112): libfprint-device-DEBUG: 17:02:47.080: Device reported finger status change: FP_FINGER_STATUS_NONE 289s (process:2112): libfprint-device-DEBUG: 17:02:47.080: Print for finger FP_FINGER_UNKNOWN enrolled 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.080: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-device-DEBUG: 17:02:47.080: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 289s (process:2112): libfprint-device-DEBUG: 17:02:47.080: Not updating temperature model, device can run continuously! 289s (process:2112): libfprint-DEBUG: 17:02:47.080: fpc_dev_template_list enter --> 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.080: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.080: fpc_send_ctrl_cmd CMD: 0x70, value: 0x0, index: 0 type: 2 289s (process:2112): libfprint-DEBUG: 17:02:47.080: fpc_cmd_receive_cb current ssm request: 112 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.080: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.081: fpc_cmd_receive_cb current ssm request: 112 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.081: fpc_cmd_receive_cb recv evt data length: 790 289s (process:2112): libfprint-DEBUG: 17:02:47.081: Query templates complete! 289s (process:2112): libfprint-device-DEBUG: 17:02:47.081: Device reported listing completion 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.081: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-device-DEBUG: 17:02:47.081: Completing action FPI_DEVICE_ACTION_LIST in idle! 289s (process:2112): libfprint-device-DEBUG: 17:02:47.081: Not updating temperature model, device can run continuously! 289s (process:2112): libfprint-device-DEBUG: 17:02:47.081: Not updating temperature model, device can run continuously! 289s (process:2112): libfprint-DEBUG: 17:02:47.081: fpc_dev_verify_identify enter --> 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.081: [fpcmoc] verify_identify entering state 0 289s (process:2112): libfprint-device-DEBUG: 17:02:47.081: Device reported finger status change: FP_FINGER_STATUS_NEEDED 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.081: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.081: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 289s (process:2112): libfprint-DEBUG: 17:02:47.082: fpc_cmd_receive_cb current ssm request: 2 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.082: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.082: fpc_cmd_receive_cb current ssm request: 2 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.082: fpc_cmd_receive_cb recv evt data length: 12 289s (process:2112): libfprint-DEBUG: 17:02:47.082: fpc_evt_cb Got finger down event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.082: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.082: [fpcmoc] verify_identify entering state 1 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.082: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.082: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.082: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.082: fpc_cmd_receive_cb current ssm request: 9 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.082: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.083: fpc_cmd_receive_cb current ssm request: 9 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.083: fpc_cmd_receive_cb recv evt data length: 24 289s (process:2112): libfprint-DEBUG: 17:02:47.083: fpc_evt_cb Got capture event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.083: Device reported finger status change: FP_FINGER_STATUS_NEEDED 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.083: [fpcmoc] verify_identify entering state 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.083: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.083: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.083: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.083: fpc_cmd_receive_cb current ssm request: 107 state: 0 289s (process:2112): libfprint-device-DEBUG: 17:02:47.083: Device reported verify result 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.083: [fpcmoc] verify_identify entering state 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.083: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.083: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.084: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.084: fpc_cmd_receive_cb current ssm request: 3 state: 0 289s (process:2112): libfprint-DEBUG: 17:02:47.084: fpc_do_abort_cb Do abort for reasons 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.084: [fpcmoc] verify_identify completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.084: Verify_identify complete! 289s (process:2112): libfprint-device-DEBUG: 17:02:47.084: Device reported verify completion 289s (process:2112): libfprint-device-DEBUG: 17:02:47.084: Device reported finger status change: FP_FINGER_STATUS_NONE 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.084: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-device-DEBUG: 17:02:47.084: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 289s (process:2112): libfprint-device-DEBUG: 17:02:47.084: Not updating temperature model, device can run continuously! 289s (process:2112): libfprint-device-DEBUG: 17:02:47.084: Not updating temperature model, device can run continuously! 289s (process:2112): libfprint-DEBUG: 17:02:47.084: fpc_dev_verify_identify enter --> 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.084: [fpcmoc] verify_identify entering state 0 289s (process:2112): libfprint-device-DEBUG: 17:02:47.084: Device reported finger status change: FP_FINGER_STATUS_NEEDED 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.084: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.084: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 289s (process:2112): libfprint-DEBUG: 17:02:47.085: fpc_cmd_receive_cb current ssm request: 2 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.085: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.085: fpc_cmd_receive_cb current ssm request: 2 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.085: fpc_cmd_receive_cb recv evt data length: 12 289s (process:2112): libfprint-DEBUG: 17:02:47.085: fpc_evt_cb Got finger down event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.085: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.085: [fpcmoc] verify_identify entering state 1 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.085: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.085: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.085: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.086: fpc_cmd_receive_cb current ssm request: 9 state: 0 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.086: [fpcmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2112): libfprint-DEBUG: 17:02:47.086: fpc_cmd_receive_cb current ssm request: 9 state: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.086: fpc_cmd_receive_cb recv evt data length: 24 289s (process:2112): libfprint-DEBUG: 17:02:47.086: fpc_evt_cb Got capture event 289s (process:2112): libfprint-device-DEBUG: 17:02:47.086: Device reported finger status change: FP_FINGER_STATUS_NEEDED 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.086: [fpcmoc] verify_identify entering state 2 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.086: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.086: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.086: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.087: fpc_cmd_receive_cb current ssm request: 107 state: 0 289s (process:2112): libfprint-device-DEBUG: 17:02:47.087: Device reported identify result 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.087: [fpcmoc] verify_identify entering state 3 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.087: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.087: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.087: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.087: fpc_cmd_receive_cb current ssm request: 3 state: 0 289s (process:2112): libfprint-DEBUG: 17:02:47.087: fpc_do_abort_cb Do abort for reasons 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.087: [fpcmoc] verify_identify completed successfully 289s (process:2112): libfprint-DEBUG: 17:02:47.087: Verify_identify complete! 289s (process:2112): libfprint-device-DEBUG: 17:02:47.087: Device reported identify completion 289s (process:2112): libfprint-device-DEBUG: 17:02:47.087: Device reported finger status change: FP_FINGER_STATUS_NONE 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.087: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-device-DEBUG: 17:02:47.087: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 289s (process:2112): libfprint-device-DEBUG: 17:02:47.087: Not updating temperature model, device can run continuously! 289s (process:2112): libfprint-DEBUG: 17:02:47.088: fpc_dev_template_delete enter --> 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.088: [fpcmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2112): libfprint-DEBUG: 17:02:47.088: fpc_send_ctrl_cmd CMD: 0x63, value: 0x0, index: 0 type: 1 289s (process:2112): libfprint-DEBUG: 17:02:47.088: fpc_dev_template_delete exit <-- 289s (process:2112): libfprint-DEBUG: 17:02:47.088: fpc_cmd_receive_cb current ssm request: 99 state: 0 289s (process:2112): libfprint-device-DEBUG: 17:02:47.088: Device reported deletion completion 289s (process:2112): libfprint-SSM-DEBUG: 17:02:47.088: [fpcmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2112): libfprint-device-DEBUG: 17:02:47.088: Completing action FPI_DEVICE_ACTION_DELETE in idle! 289s (process:2112): libfprint-device-DEBUG: 17:02:47.088: Not updating temperature model, device can run continuously! 289s (process:2112): libfprint-DEBUG: 17:02:47.088: fpc_dev_close enter --> 289s (process:2112): libfprint-device-DEBUG: 17:02:47.088: Device reported close completion 289s (process:2112): libfprint-device-DEBUG: 17:02:47.089: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s (process:2112): libfprint-device-DEBUG: 17:02:47.089: Not updating temperature model, device can run continuously! 289s Clear 289s Clear done 289s enrolling 289s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf43c7e171180 (FpiDeviceFpcMoc at 0x2fe7e140)>, 1, None, None, None) 289s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf43c7e171180 (FpiDeviceFpcMoc at 0x2fe7e140)>, 2, None, None, None) 289s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf43c7e171180 (FpiDeviceFpcMoc at 0x2fe7e140)>, 3, None, None, None) 289s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf43c7e171180 (FpiDeviceFpcMoc at 0x2fe7e140)>, 4, None, None, None) 289s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf43c7e171180 (FpiDeviceFpcMoc at 0x2fe7e140)>, 5, None, None, None) 289s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf43c7e171180 (FpiDeviceFpcMoc at 0x2fe7e140)>, 5, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3)) 289s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf43c7e171180 (FpiDeviceFpcMoc at 0x2fe7e140)>, 6, None, None, None) 289s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf43c7e171180 (FpiDeviceFpcMoc at 0x2fe7e140)>, 7, None, None, None) 289s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf43c7e171180 (FpiDeviceFpcMoc at 0x2fe7e140)>, 7, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3)) 289s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf43c7e171180 (FpiDeviceFpcMoc at 0x2fe7e140)>, 8, None, None, None) 289s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf43c7e171180 (FpiDeviceFpcMoc at 0x2fe7e140)>, 9, None, None, None) 289s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf43c7e171180 (FpiDeviceFpcMoc at 0x2fe7e140)>, 10, None, None, None) 289s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf43c7e171180 (FpiDeviceFpcMoc at 0x2fe7e140)>, 10, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3)) 289s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf43c7e171180 (FpiDeviceFpcMoc at 0x2fe7e140)>, 11, None, None, None) 289s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf43c7e171180 (FpiDeviceFpcMoc at 0x2fe7e140)>, 12, None, None, None) 289s enroll done 289s listing 289s listing done 289s verifying 289s verify done 289s async identifying 289s indentification_done: 289s deleting 289s delete done 289s ** (umockdev-run:2108): DEBUG: 17:02:47.101: umockdev.vala:150: Removing test bed /tmp/umockdev.AES3J2 289s (umockdev-run:2108): GLib-DEBUG: 17:02:47.104: unsetenv() is not thread-safe and should not be used after threads are created 289s PASS: libfprint-2/driver-fpcmoc.test 289s Running test: libfprint-2/driver-uru4000-4500.test 289s ** (umockdev-run:2120): DEBUG: 17:02:47.150: umockdev.vala:123: Created udev test bed /tmp/umockdev.2QM8J2 289s ** (umockdev-run:2120): DEBUG: 17:02:47.150: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 289s ** (umockdev-run:2120): DEBUG: 17:02:47.151: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 289s ** (umockdev-run:2120): DEBUG: 17:02:47.153: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.2QM8J2/dev/bus/usb/001/050 289s ** (umockdev-run:2120): DEBUG: 17:02:47.153: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 289s ** (umockdev-run:2120): DEBUG: 17:02:47.154: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 289s ** (umockdev-run:2120): DEBUG: 17:02:47.156: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.2QM8J2/dev/bus/usb/001/001 289s ** (umockdev-run:2120): DEBUG: 17:02:47.156: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 289s ** (umockdev-run:2120): DEBUG: 17:02:47.156: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 289s (process:2124): libfprint-context-DEBUG: 17:02:47.207: Initializing FpContext (libfprint version 1.94.7+tod1) 289s (process:2124): libfprint-tod-DEBUG: 17:02:47.208: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 289s (process:2124): libfprint-context-DEBUG: 17:02:47.209: No driver found for USB device 1D6B:0002 289s (process:2124): libfprint-device-DEBUG: 17:02:47.210: Device reported probe completion 289s (process:2124): libfprint-device-DEBUG: 17:02:47.210: Completing action FPI_DEVICE_ACTION_PROBE in idle! 289s (process:2124): libfprint-device-DEBUG: 17:02:47.210: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find ha(process:2124): GLib-DEBUG: 17:02:47.213: setenv()/putenv() are not thread-safe and should not be used after threads are created 289s (process:2124): libfprint-image_device-DEBUG: 17:02:47.233: Image device open completed 289s ndle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s (process:2124): libfprint-device-DEBUG: 17:02:47.233: Device reported open completion 289s (process:2124): libfprint-device-DEBUG: 17:02:47.233: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s (process:2124): libfprint-device-DEBUG: 17:02:47.233: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s (process:2124): libfprint-device-DEBUG: 17:02:47.234: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s (process:2124): libfprint-image_device-DEBUG: 17:02:47.234: Activating image device 289s (process:2124): libfprint-image_device-DEBUG: 17:02:47.234: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 289s (process:2124): libfprint-SSM-DEBUG: 17:02:47.234: [uru4000] INIT_NUM_STATES entering state 0 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.234: read 1 regs at 7 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.235: reg value 1 289s (process:2124): libfprint-SSM-DEBUG: 17:02:47.235: [uru4000] INIT_NUM_STATES entering state 1 289s (process:2124): libfprint-SSM-DEBUG: 17:02:47.235: [uru4000] INIT_NUM_STATES entering state 3 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.235: set 81 289s (process:2124): libfprint-SSM-DEBUG: 17:02:47.235: [uru4000] INIT_NUM_STATES entering state 4 289s (process:2124): libfprint-SSM-DEBUG: 17:02:47.235: [uru4000] POWERUP_NUM_STATES entering state 0 289s (process:2124): libfprint-SSM-DEBUG: 17:02:47.235: [uru4000] POWERUP_NUM_STATES entering state 1 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.235: set 01 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.236: recv irq type 56aa 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.236: early scanpwr interrupt 289s (process:2124): libfprint-SSM-DEBUG: 17:02:47.236: [uru4000] POWERUP_NUM_STATES entering state 2 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.236: read 1 regs at 7 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.237: reg value 1 289s (process:2124): libfprint-SSM-DEBUG: 17:02:47.237: [uru4000] POWERUP_NUM_STATES entering state 3 289s (process:2124): libfprint-SSM-DEBUG: 17:02:47.237: [uru4000] POWERUP_NUM_STATES completed successfully 289s (process:2124): libfprint-SSM-DEBUG: 17:02:47.237: [uru4000] INIT_NUM_STATES entering state 5 289s (process:2124): libfprint-SSM-DEBUG: 17:02:47.237: [uru4000] INIT_NUM_STATES entering state 6 289s (process:2124): libfprint-SSM-DEBUG: 17:02:47.237: [uru4000] INIT_NUM_STATES entering state 7 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.237: read 16 regs at f0 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.237: reg value 1a 289s (process:2124): libfprint-SSM-DEBUG: 17:02:47.237: [uru4000] INIT_NUM_STATES entering state 8 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.237: Versions 0010 and 0115 289s (process:2124): libfprint-SSM-DEBUG: 17:02:47.237: [uru4000] INIT_NUM_STATES completed successfully 289s (process:2124): libfprint-image_device-DEBUG: 17:02:47.237: Image device activation completed 289s (process:2124): libfprint-image_device-DEBUG: 17:02:47.237: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 289s (process:2124): libfprint-image_device-DEBUG: 17:02:47.237: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.237: wait finger on 289s (process:2124): libfprint-device-DEBUG: 17:02:47.238: Device reported finger status change: FP_FINGER_STATUS_NEEDED 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.238: recv irq type 56aa 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.239: recv irq type 56aa 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.239: recv irq type 0101 289s (process:2124): libfprint-device-DEBUG: 17:02:47.239: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 289s (process:2124): libfprint-image_device-DEBUG: 17:02:47.239: Image device reported finger status: on 289s (process:2124): libfprint-image_device-DEBUG: 17:02:47.239: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.239: starting capture 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.239: Image encryption seed: 1374298404 289s (process:2124): libfprint-SSM-DEBUG: 17:02:47.239: [uru4000] IMAGING_NUM_STATES entering state 0 289s (process:2124): libfprint-SSM-DEBUG: 17:02:47.240: [uru4000] IMAGING_NUM_STATES entering state 1 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.240: hw header lines 289 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.241: dev2: 11240 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.241: image seems to be encrypted 289s (process:2124): libfprint-SSM-DEBUG: 17:02:47.241: [uru4000] IMAGING_NUM_STATES entering state 2 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.241: read 4 regs at 34 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.241: reg value f2 289s (process:2124): libfprint-SSM-DEBUG: 17:02:47.241: [uru4000] IMAGING_NUM_STATES entering state 3 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.241: encryption id 00 -> key 544409d6 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.241: 0 02 72 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.241: decoding 72 lines 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.242: 1 00 1 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.242: skipping 1 lines 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.242: 2 02 49 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.242: decoding 49 lines 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.242: 3 01 1 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.242: skipping 1 lines 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.242: 4 00 1 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.242: skipping 1 lines 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.242: 5 02 49 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.242: decoding 49 lines 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.242: 6 00 1 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.242: skipping 1 lines 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.242: 7 02 116 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.242: decoding 116 lines 289s (process:2124): libfprint-SSM-DEBUG: 17:02:47.242: [uru4000] IMAGING_NUM_STATES entering state 4 289s (process:2124): libfprint-image_device-DEBUG: 17:02:47.242: Image device captured an image 289s (process:2124): libfprint-image_device-DEBUG: 17:02:47.247: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 289s (process:2124): libfprint-device-DEBUG: 17:02:47.247: Device reported finger status change: FP_FINGER_STATUS_PRESENT 289s (process:2124): libfprint-SSM-DEBUG: 17:02:47.247: [uru4000] IMAGING_NUM_STATES completed successfully 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.247: await finger off 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.247: recv irq type 0200 289s (process:2124): libfprint-device-DEBUG: 17:02:47.248: Device reported finger status change: FP_FINGER_STATUS_NONE 289s (process:2124): libfprint-image_device-DEBUG: 17:02:47.248: Image device reported finger status: off 289s (process:2124): libfprint-image_device-DEBUG: 17:02:47.248: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 289s (process:2124): libfprint-image_device-DEBUG: 17:02:47.248: Deactivating image device 289s (process:2124): libfprint-image_device-DEBUG: 17:02:47.248: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.248: deactivating 289s (process:2124): libfprint-uru4000-DEBUG: 17:02:47.248: cancelled 289s (process:2124): libfprint-image_device-DEBUG: 17:02:47.248: Image device deactivation completed 289s (process:2124): libfprint-image_device-DEBUG: 17:02:47.248: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 289s (process:2124): libfprint-image-DEBUG: 17:02:47.282: Minutiae scan completed in 0.039555 secs 289s (process:2124): libfprint-device-DEBUG: 17:02:47.283: Device reported capture completion 289s (process:2124): libfprint-device-DEBUG: 17:02:47.283: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 289s (process:2124): libfprint-device-DEBUG: 17:02:47.283: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 289s (process:2124): libfprint-image_device-DEBUG: 17:02:47.284: Image device close completed 289s (process:2124): libfprint-device-DEBUG: 17:02:47.284: Device reported close completion 289s (process:2124): libfprint-device-DEBUG: 17:02:47.284: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s (process:2124): libfprint-device-DEBUG: 17:02:47.284: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s ** (umockdev-run:2120): DEBUG: 17:02:47.423: umockdev.vala:150: Removing test bed /tmp/umockdev.2QM8J2 289s (umockdev-run:2120): GLib-DEBUG: 17:02:47.426: unsetenv() is not thread-safe and should not be used after threads are created 289s Comparing PNGs /tmp/libfprint-umockdev-test-y49jgg7g/capture.png and /usr/share/installed-tests/libfprint-2/uru4000-4500/capture.png 289s PASS: libfprint-2/driver-uru4000-4500.test 289s Running test: libfprint-2/driver-elanmoc.test 289s ** (umockdev-run:2133): DEBUG: 17:02:47.504: umockdev.vala:123: Created udev test bed /tmp/umockdev.F93DK2 289s ** (umockdev-run:2133): DEBUG: 17:02:47.504: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 289s ** (umockdev-run:2133): DEBUG: 17:02:47.505: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 289s ** (umockdev-run:2133): DEBUG: 17:02:47.507: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.F93DK2/dev/bus/usb/001/003 289s ** (umockdev-run:2133): DEBUG: 17:02:47.508: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 289s ** (umockdev-run:2133): DEBUG: 17:02:47.508: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 289s ** (umockdev-run:2133): DEBUG: 17:02:47.510: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.F93DK2/dev/bus/usb/001/001 289s ** (umockdev-run:2133): DEBUG: 17:02:47.510: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 289s ** (umockdev-run:2133): DEBUG: 17:02:47.511: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 289s (process:2137): libfprint-context-DEBUG: 17:02:47.556: Initializing FpContext (libfprint version 1.94.7+tod1) 289s (process:2137): libfprint-tod-DEBUG: 17:02:47.556: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 289s (process:2137): libfprint-elanmoc-DEBUG: 17:02:47.558: 123543192: ../libfprint/drivers/elanmoc/elanmoc.c:1150 289s (process:2137): libfprint-context-DEBUG: 17:02:47.558: No driver found for USB device 1D6B:0002 289s (process:2137): libfprint-device-DEBUG: 17:02:47.558: Device reported probe completion 289s (process:2137): libfprint-device-DEBUG: 17:02:47.558: Completing action FPI_DEVICE_ACTION_PROBE in idle! 289s (process:2137): libfprint-device-DEBUG: 17:02:47.558: Not updating temperature model, device can run continuously! 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find ha(process:2137): libfprint-SSM-DEBUG: 17:02:47.561: [elanmoc] DEV_INIT_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.562: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.562: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.562: [elanmoc] DEV_INIT_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.562: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.563: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.563: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.563: [elanmoc] DEV_INIT_STATES entering state 2 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.563: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.564: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.564: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-elanmoc-DEBUG: 17:02:47.564: elanmoc FW Version 8004 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.564: [elanmoc] DEV_INIT_STATES entering state 3 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.564: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.564: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.565: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-elanmoc-DEBUG: 17:02:47.565: elanmoc last_read DIM 0x57(87) 0x6B(107) 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.565: [elanmoc] DEV_INIT_STATES entering state 4 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.565: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.565: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.566: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-elanmoc-DEBUG: 17:02:47.566: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.566: [elanmoc] DEV_INIT_STATES completed successfully 289s (process:2137): libfprint-device-DEBUG: 17:02:47.566: Device reported open completion 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.566: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-device-DEBUG: 17:02:47.566: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s (process:2137): libfprint-device-DEBUG: 17:02:47.566: Not updating temperature model, device can run continuously! 289s (process:2137): libfprint-device-DEBUG: 17:02:47.567: Not updating temperature model, device can run continuously! 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.567: [elanmoc] MOC_ENROLL_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.567: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.568: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-elanmoc-DEBUG: 17:02:47.568: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 289s ndle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s libusb: error [op_handle_events] cannot find handle for fd 9 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.568: [elanmoc] MOC_ENROLL_NUM_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.568: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.569: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.569: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-elanmoc-DEBUG: 17:02:47.569: ##### Re-Enrollment Case! ##### 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.569: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.569: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.569: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.570: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-device-DEBUG: 17:02:47.570: Device reported enroll progress, reported 1 of 9 have been completed 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.570: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.570: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.571: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.571: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-device-DEBUG: 17:02:47.571: Device reported enroll progress, reported 2 of 9 have been completed 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.571: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.571: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.572: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.572: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-device-DEBUG: 17:02:47.572: Device reported enroll progress, reported 3 of 9 have been completed 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.572: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.572: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.572: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.573: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-device-DEBUG: 17:02:47.573: Device reported enroll progress, reported 4 of 9 have been completed 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.573: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.573: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.573: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.574: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-device-DEBUG: 17:02:47.574: Device reported enroll progress, reported 5 of 9 have been completed 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.574: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.574: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.574: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.575: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-device-DEBUG: 17:02:47.575: Device reported enroll progress, reported 6 of 9 have been completed 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.575: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.575: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.575: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.576: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-device-DEBUG: 17:02:47.576: Device reported enroll progress, reported 7 of 9 have been completed 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.576: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.576: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.576: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.576: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-device-DEBUG: 17:02:47.577: Device reported enroll progress, reported 7 of 9 have been completed 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.577: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.577: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.577: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.577: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-device-DEBUG: 17:02:47.578: Device reported enroll progress, reported 8 of 9 have been completed 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.578: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.578: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.578: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.578: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-device-DEBUG: 17:02:47.579: Device reported enroll progress, reported 8 of 9 have been completed 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.579: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.579: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.579: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.579: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-device-DEBUG: 17:02:47.580: Device reported enroll progress, reported 9 of 9 have been completed 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.580: [elanmoc] MOC_ENROLL_NUM_STATES entering state 3 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.580: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.580: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.580: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-elanmoc-DEBUG: 17:02:47.581: elanmoc_commit_cb success 289s (process:2137): libfprint-elanmoc-DEBUG: 17:02:47.581: Enrollment was successful! 289s (process:2137): libfprint-device-DEBUG: 17:02:47.581: Device reported enroll completion 289s (process:2137): libfprint-device-DEBUG: 17:02:47.581: Print for finger FP_FINGER_UNKNOWN enrolled 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.581: [elanmoc] MOC_ENROLL_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.581: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-device-DEBUG: 17:02:47.581: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 289s (process:2137): libfprint-device-DEBUG: 17:02:47.581: Not updating temperature model, device can run continuously! 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.581: [elanmoc] MOC_LIST_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.581: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.581: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-elanmoc-DEBUG: 17:02:47.582: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.582: [elanmoc] MOC_LIST_NUM_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.582: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.582: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.582: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.583: [elanmoc] MOC_LIST_NUM_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.583: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.583: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.583: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.583: [elanmoc] MOC_LIST_NUM_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.583: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.584: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.584: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.584: [elanmoc] MOC_LIST_NUM_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.584: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.585: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.585: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.585: [elanmoc] MOC_LIST_NUM_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.585: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.585: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.586: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.586: [elanmoc] MOC_LIST_NUM_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.586: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.586: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.586: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.587: [elanmoc] MOC_LIST_NUM_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.587: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.587: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.587: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.588: [elanmoc] MOC_LIST_NUM_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.588: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.588: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.588: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.589: [elanmoc] MOC_LIST_NUM_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.589: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.589: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.589: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.590: [elanmoc] MOC_LIST_NUM_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.590: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.590: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.590: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-device-DEBUG: 17:02:47.590: Device reported listing completion 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.590: [elanmoc] MOC_LIST_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.590: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-device-DEBUG: 17:02:47.590: Completing action FPI_DEVICE_ACTION_LIST in idle! 289s (process:2137): libfprint-device-DEBUG: 17:02:47.590: Not updating temperature model, device can run continuously! 289s (process:2137): libfprint-device-DEBUG: 17:02:47.591: Not updating temperature model, device can run continuously! 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.591: [elanmoc] IDENTIFY_NUM_STATES entering state 0 289s (process:2137): libfprint-elanmoc-DEBUG: 17:02:47.591: elanmoc elan_identify_run_state 289s (process:2137): libfprint-elanmoc-DEBUG: 17:02:47.591: elanmoc elan_identify_run_state IDENTIFY_SET_MODE 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.591: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.591: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.592: [elanmoc] IDENTIFY_NUM_STATES entering state 1 289s (process:2137): libfprint-elanmoc-DEBUG: 17:02:47.592: elanmoc elan_identify_run_state 289s (process:2137): libfprint-elanmoc-DEBUG: 17:02:47.592: elanmoc elan_identify_run_state VERIFY_WAIT_FINGER 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.592: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.592: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.592: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-elanmoc-DEBUG: 17:02:47.592: Verify was successful! for user: 0 mesg_code: 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.592: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.593: [elanmoc] IDENTIFY_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.593: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.593: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-elanmoc-DEBUG: 17:02:47.593: Verify/Identify successful for: FP1-00000000-0-00000000-nobody 289s (process:2137): libfprint-device-DEBUG: 17:02:47.593: Device reported verify result 289s (process:2137): libfprint-device-DEBUG: 17:02:47.593: Device reported verify completion 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.593: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-device-DEBUG: 17:02:47.593: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 289s (process:2137): libfprint-device-DEBUG: 17:02:47.593: Not updating temperature model, device can run continuously! 289s (process:2137): libfprint-device-DEBUG: 17:02:47.594: Not updating temperature model, device can run continuously! 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.594: [elanmoc] IDENTIFY_NUM_STATES entering state 0 289s (process:2137): libfprint-elanmoc-DEBUG: 17:02:47.594: elanmoc elan_identify_run_state 289s (process:2137): libfprint-elanmoc-DEBUG: 17:02:47.594: elanmoc elan_identify_run_state IDENTIFY_SET_MODE 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.594: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.594: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.595: [elanmoc] IDENTIFY_NUM_STATES entering state 1 289s (process:2137): libfprint-elanmoc-DEBUG: 17:02:47.595: elanmoc elan_identify_run_state 289s (process:2137): libfprint-elanmoc-DEBUG: 17:02:47.595: elanmoc elan_identify_run_state VERIFY_WAIT_FINGER 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.595: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.595: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.595: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-elanmoc-DEBUG: 17:02:47.596: Verify was successful! for user: 0 mesg_code: 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.596: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.596: [elanmoc] IDENTIFY_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.596: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.596: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-elanmoc-DEBUG: 17:02:47.596: Verify/Identify successful for: FP1-00000000-0-00000000-nobody 289s (process:2137): libfprint-device-DEBUG: 17:02:47.597: Device reported identify result 289s (process:2137): libfprint-device-DEBUG: 17:02:47.597: Device reported identify completion 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.597: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-device-DEBUG: 17:02:47.597: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 289s (process:2137): libfprint-device-DEBUG: 17:02:47.597: Not updating temperature model, device can run continuously! 289s (process:2137): libfprint-elanmoc-DEBUG: 17:02:47.597: Delete Finger, user_id = FP1-00000000-0-00000000-nobody! 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.597: [elanmoc] DELETE_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.597: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.597: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-device-DEBUG: 17:02:47.598: Device reported deletion completion 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.598: [elanmoc] DELETE_NUM_STATES completed successfully 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.598: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-device-DEBUG: 17:02:47.598: Completing action FPI_DEVICE_ACTION_DELETE in idle! 289s (process:2137): libfprint-device-DEBUG: 17:02:47.598: Not updating temperature model, device can run continuously! 289s (process:2137): libfprint-elanmoc-DEBUG: 17:02:47.598: Elanmoc dev_exit 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.598: [elanmoc] DEV_EXIT_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.598: [elanmoc] FP_CMD_NUM_STATES entering state 0 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.598: [elanmoc] FP_CMD_NUM_STATES entering state 1 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.598: [elanmoc] DEV_EXIT_STATES completed successfully 289s (process:2137): libfprint-device-DEBUG: 17:02:47.599: Device reported close completion 289s (process:2137): libfprint-SSM-DEBUG: 17:02:47.599: [elanmoc] FP_CMD_NUM_STATES completed successfully 289s (process:2137): libfprint-device-DEBUG: 17:02:47.599: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s (process:2137): libfprint-device-DEBUG: 17:02:47.599: Not updating temperature model, device can run continuously! 289s enrolling 289s finger status: 289s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf713708b9340 (FpiDeviceElanmoc at 0x2c77e00)>, 1, None, None, None) 289s finger status: 289s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf713708b9340 (FpiDeviceElanmoc at 0x2c77e00)>, 2, None, None, None) 289s finger status: 289s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf713708b9340 (FpiDeviceElanmoc at 0x2c77e00)>, 3, None, None, None) 289s finger status: 289s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf713708b9340 (FpiDeviceElanmoc at 0x2c77e00)>, 4, None, None, None) 289s finger status: 289s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf713708b9340 (FpiDeviceElanmoc at 0x2c77e00)>, 5, None, None, None) 289s finger status: 289s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf713708b9340 (FpiDeviceElanmoc at 0x2c77e00)>, 6, None, None, None) 289s finger status: 289s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf713708b9340 (FpiDeviceElanmoc at 0x2c77e00)>, 7, None, None, None) 289s finger status: 289s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf713708b9340 (FpiDeviceElanmoc at 0x2c77e00)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 289s finger status: 289s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf713708b9340 (FpiDeviceElanmoc at 0x2c77e00)>, 8, None, None, None) 289s finger status: 289s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf713708b9340 (FpiDeviceElanmoc at 0x2c77e00)>, 8, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 289s finger status: 289s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xf713708b9340 (FpiDeviceElanmoc at 0x2c77e00)>, 9, None, None, None) 289s enroll done 289s listing 289s listing done 289s verifying 289s verify done 289s async identifying 289s indentification_done: 289s deleting 289s delete done 289s ** (umockdev-run:2133): DEBUG: 17:02:47.609: umockdev.vala:150: Removing test bed /tmp/umockdev.F93DK2 289s (umockdev-run:2133): GLib-DEBUG: 17:02:47.613: unsetenv() is not thread-safe and should not be used after threads are created 289s PASS: libfprint-2/driver-elanmoc.test 289s Running test: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 289s (process:2143): libfprint-context-DEBUG: 17:02:47.628: Initializing FpContext (libfprint version 1.94.7+tod1) 289s (process:2143): libfprint-tod-DEBUG: 17:02:47.628: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 289s (process:2143): libfprint-tod-DEBUG: 17:02:47.629: Found TOD entry point symbol 0xed0fec962580, GType is 205685014394336 289s (process:2143): libfprint-tod-DEBUG: 17:02:47.629: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 289s (process:2143): libfprint-context-DEBUG: 17:02:47.629: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 289s (process:2143): libfprint-context-DEBUG: 17:02:47.630: created 289s (process:2143): libfprint-fake_test_dev_tod_current-DEBUG: 17:02:47.630: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 289s 289s (process:2143): libfprint-device-DEBUG: 17:02:47.630: Device reported probe completion 289s (process:2143): libfprint-device-DEBUG: 17:02:47.630: Completing action FPI_DEVICE_ACTION_PROBE in idle! 289s (process:2143): libfprint-device-DEBUG: 17:02:47.630: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s (/usr/libexec/installed-tests/libfprint-2/test-fpi-device-tod:2143): GLib-DEBUG: 17:02:47.630: setenv()/putenv() are not thread-safe and should not be used after threads are created 289s TAP version 13 289s # random seed: R02Sb15c910e03586d525df0834cb558558a 289s 1..97 289s # Start of driver tests 289s ok 1 /driver/get_driver 289s ok 2 /driver/get_device_id 289s ok 3 /driver/get_name 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s ok 4 /driver/is_open 289s ok 5 /driver/get_nr_enroll_stages 289s ok 6 /driver/set_nr_enroll_stages 289s ok 7 /driver/supports_identify 289s ok 8 /driver/supports_capture 289s ok 9 /driver/has_storage 289s ok 10 /driver/do_not_support_identify 289s ok 11 /driver/do_not_support_capture 289s ok 12 /driver/has_not_storage 289s ok 13 /driver/get_usb_device 289s ok 14 /driver/get_virtual_env 289s ok 15 /driver/get_driver_data 289s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 289s # libfprint-device-DEBUG: Tod version info is 'current' 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 289s # 289s # libfprint-device-DEBUG: Device reported probe completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 289s # libfprint-device-DEBUG: Tod version info is 'current' 289s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 289s # libfprint-device-DEBUG: Tod version info is 'current' 289s ok 16 /driver/initial_features 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Probed device name in action FPI_DEVICE_ACTION_PROBE 289s # 289s # libfprint-device-DEBUG: Device reported probe completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s ok 17 /driver/probe 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s ok 18 /driver/open 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s ok 19 /driver/close 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 289s # 289s # libfprint-device-DEBUG: Device reported enroll completion 289s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s ok 20 /driver/enroll 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 289s # 289s # libfprint-device-DEBUG: Device reported verify result 289s # libfprint-device-DEBUG: Device reported verify completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s ok 21 /driver/verify 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 289s # 289s # libfprint-device-DEBUG: Device reported identify result 289s # libfprint-device-DEBUG: Device reported identify completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s ok 22 /driver/identify 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 289s # 289s # libfprint-device-DEBUG: Device reported capture completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s ok 23 /driver/capture 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 289s # 289s # libfprint-device-DEBUG: Device reported listing completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s ok 24 /driver/list 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 289s # 289s # libfprint-device-DEBUG: Device reported deletion completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s ok 25 /driver/delete 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 289s # libfprint-device-DEBUG: Tod version info is 'current' 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 289s # 289s # libfprint-device-DEBUG: Device reported deletion completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s ok 26 /driver/clear_storage 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 289s # 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 289s # 289s # libfprint-device-DEBUG: Device reported deletion completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s ok 27 /driver/cancel 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 289s # libfprint-device-DEBUG: Tod version info is 'current' 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 289s # 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 289s # 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 289s # 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 289s # 289s # libfprint-device-DEBUG: Device reported verify result 289s # libfprint-device-DEBUG: Device reported verify completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s ok 28 /driver/critical 289s ok 29 /driver/get_current_action 289s ok 30 /driver/timeout 289s ok 31 /driver/error_types 289s ok 32 /driver/retry_error_types 289s # Start of get_scan_type tests 289s ok 33 /driver/get_scan_type/press 289s ok 34 /driver/get_scan_type/swipe 289s # End of get_scan_type tests 289s # Start of set_scan_type tests 289s ok 35 /driver/set_scan_type/press 289s ok 36 /driver/set_scan_type/swipe 289s # End of set_scan_type tests 289s # Start of finger_status tests 289s ok 37 /driver/finger_status/inactive 289s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 289s ok 38 /driver/finger_status/waiting 289s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 289s ok 39 /driver/finger_status/present 289s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 289s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 289s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 289s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 289s ok 40 /driver/finger_status/changes 289s # End of finger_status tests 289s # Start of features tests 289s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 289s # libfprint-device-DEBUG: Tod version info is 'current' 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 289s # 289s # libfprint-device-DEBUG: Device reported probe completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s ok 41 /driver/features/probe_updates 289s # End of features tests 289s # Start of initial_features tests 289s ok 42 /driver/initial_features/none 289s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 289s # libfprint-device-DEBUG: Tod version info is 'current' 289s ok 43 /driver/initial_features/no_capture 289s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 289s # libfprint-device-DEBUG: Tod version info is 'current' 289s ok 44 /driver/initial_features/no_verify 289s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 289s # libfprint-device-DEBUG: Tod version info is 'current' 289s ok 45 /driver/initial_features/no_identify 289s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 289s # libfprint-device-DEBUG: Tod version info is 'current' 289s ok 46 /driver/initial_features/no_storage 289s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 289s # libfprint-device-DEBUG: Tod version info is 'current' 289s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 289s # libfprint-device-DEBUG: Tod version info is 'current' 289s ok 47 /driver/initial_features/no_list 289s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 289s # libfprint-device-DEBUG: Tod version info is 'current' 289s ok 48 /driver/initial_features/no_delete 289s ok 49 /driver/initial_features/no_clear 289s # End of initial_features tests 289s # Start of probe tests 289s # libfprint-device-DEBUG: Device reported probe completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s ok 50 /driver/probe/error 289s # libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE 289s # libfprint-device-DEBUG: Device reported probe completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s ok 51 /driver/probe/action_error 289s # End of probe tests 289s # Start of open tests 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s ok 52 /driver/open/error 289s # End of open tests 289s # Start of close tests 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s ok 53 /driver/close/error 289s # End of close tests 289s # Start of enroll tests 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 289s # 289s # libfprint-device-DEBUG: Device reported enroll completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s ok 54 /driver/enroll/error 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Device reported enroll progress, reported 1408154893 of 985562706 have been completed 289s # libfprint-device-DEBUG: Device reported enroll progress, reported 1589554979 of 985562706 have been completed 289s # libfprint-device-DEBUG: Device reported enroll progress, reported 1004884544 of 985562706 have been completed 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 289s # 289s # libfprint-device-DEBUG: Device reported enroll completion 289s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s ok 55 /driver/enroll/progress 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 289s # 289s # libfprint-device-DEBUG: Device reported enroll completion 289s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s ok 56 /driver/enroll/update_nbis 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s ok 57 /driver/enroll/update_nbis_wrong_device 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s ok 58 /driver/enroll/update_nbis_wrong_driver 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s ok 59 /driver/enroll/update_nbis_missing_feature 289s # Start of error tests 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Device reported enroll completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s # libfprint-device-DEBUG: Device reported enroll completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s # libfprint-device-DEBUG: Device reported enroll completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s ok 60 /driver/enroll/error/no_print 289s # End of error tests 289s # End of enroll tests 289s # Start of verify tests 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 289s # 289s # libfprint-device-DEBUG: Device reported verify result 289s # libfprint-device-DEBUG: Device reported verify completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s ok 61 /driver/verify/fail 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 289s # 289s # libfprint-device-DEBUG: Device reported verify result 289s # libfprint-device-DEBUG: Device reported verify completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s ok 62 /driver/verify/retry 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 289s # 289s # libfprint-device-DEBUG: Device reported verify completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s ok 63 /driver/verify/error 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s ok 64 /driver/verify/not_supported 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Device reported verify result 289s # libfprint-device-DEBUG: Device reported verify completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s ok 65 /driver/verify/report_no_cb 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Device reported verify completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s ok 66 /driver/verify/not_reported 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Device reported verify result 289s # libfprint-device-DEBUG: Device reported verify completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s # libfprint-device-DEBUG: Device reported verify result 289s # libfprint-device-DEBUG: Device reported verify completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s # libfprint-device-DEBUG: Device reported verify result 289s # libfprint-device-DEBUG: Device reported verify completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s # libfprint-device-DEBUG: Device reported verify result 289s # libfprint-device-DEBUG: Device reported verify completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s # libfprint-device-DEBUG: Device reported verify result 289s # libfprint-device-DEBUG: Device reported verify completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s ok 67 /driver/verify/complete_retry 289s # End of verify tests 289s # Start of identify tests 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 289s # 289s # libfprint-device-DEBUG: Device reported identify result 289s # libfprint-device-DEBUG: Device reported identify completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s ok 68 /driver/identify/fail 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 289s # 289s # libfprint-device-DEBUG: Device reported identify result 289s # libfprint-device-DEBUG: Device reported identify completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s ok 69 /driver/identify/retry 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 289s # 289s # libfprint-device-DEBUG: Device reported identify completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s ok 70 /driver/identify/error 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Device reported identify completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s ok 71 /driver/identify/not_reported 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Device reported identify result 289s # libfprint-device-DEBUG: Device reported identify completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s # libfprint-device-DEBUG: Device reported identify result 289s # libfprint-device-DEBUG: Device reported identify completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s # libfprint-device-DEBUG: Device reported identify result 289s # libfprint-device-DEBUG: Device reported identify completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s ok 72 /driver/identify/complete_retry 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Device reported identify result 289s # libfprint-device-DEBUG: Device reported identify completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s ok 73 /driver/identify/report_no_cb 289s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 289s # libfprint-device-DEBUG: Tod version info is 'current' 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 289s # 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 289s # 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 289s # 289s # libfprint-device-DEBUG: Device reported identify result 289s # libfprint-device-DEBUG: Device reported identify completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s ok 74 /driver/identify/suspend_continues 289s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 289s # libfprint-device-DEBUG: Tod version info is 'current' 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 289s # 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 289s # 289s # libfprint-device-DEBUG: Device reported identify result 289s # libfprint-device-DEBUG: Device reported identify completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s ok 75 /driver/identify/suspend_succeeds 289s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 289s # libfprint-device-DEBUG: Tod version info is 'current' 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 289s # 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 289s # 289s # libfprint-device-DEBUG: Device reported identify completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 289s ok 76 /driver/identify/suspend_busy_error 289s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 289s # libfprint-device-DEBUG: Tod version info is 'current' 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 289s # 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s ok 77 /driver/identify/suspend_while_idle 289s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 289s # libfprint-device-DEBUG: Tod version info is 'current' 289s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 289s # 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.30, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 291s # libfprint-device-DEBUG: Updated temperature model after 2.00 seconds, ratio 0.30 -> 0.74, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_HOT 291s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 291s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 291s # 291s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 291s # 291s # libfprint-device-DEBUG: Device reported identify completion 291s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 291s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 291s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 1 -> 1, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 291s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 293s Executing: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 294s # libfprint-device-DEBUG: Updated temperature model after 2.09 seconds, ratio 0.74 -> 0.49, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_WARM 297s # libfprint-device-DEBUG: Updated temperature model after 3.10 seconds, ratio 0.49 -> 0.26, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 297s # 297s # libfprint-device-DEBUG: Device reported close completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.26 -> 0.26, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s ok 78 /driver/identify/warmup_cooldown 297s # slow test /driver/identify/warmup_cooldown executed in 7.29 secs 297s # End of identify tests 297s # Start of capture tests 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 297s # 297s # libfprint-device-DEBUG: Device reported open completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 297s # 297s # libfprint-device-DEBUG: Device reported close completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s ok 79 /driver/capture/not_supported 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 297s # 297s # libfprint-device-DEBUG: Device reported open completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 297s # 297s # libfprint-device-DEBUG: Device reported capture completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 297s # 297s # libfprint-device-DEBUG: Device reported close completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 297s ok 80 /driver/capture/error 297s # End of capture tests 297s # Start of list tests 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 297s # 297s # libfprint-device-DEBUG: Device reported open completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 297s # 297s # libfprint-device-DEBUG: Device reported listing completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 297s # 297s # libfprint-device-DEBUG: Device reported close completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s ok 81 /driver/list/error 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 297s # 297s # libfprint-device-DEBUG: Device reported open completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 297s # 297s # libfprint-device-DEBUG: Device reported close completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s ok 82 /driver/list/no_storage 297s # End of list tests 297s # Start of delete tests 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 297s # 297s # libfprint-device-DEBUG: Device reported open completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 297s # 297s # libfprint-device-DEBUG: Device reported deletion completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 297s # 297s # libfprint-device-DEBUG: Device reported close completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s ok 83 /driver/delete/error 297s # End of delete tests 297s # Start of clear_storage tests 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 297s # 297s # libfprint-device-DEBUG: Device reported open completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 297s # libfprint-device-DEBUG: Tod version info is 'current' 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 297s # 297s # libfprint-device-DEBUG: Device reported deletion completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 297s # 297s # libfprint-device-DEBUG: Device reported close completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s ok 84 /driver/clear_storage/error 297s # End of clear_storage tests 297s # Start of cancel tests 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 297s # 297s # libfprint-device-DEBUG: Device reported open completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 297s # 297s # libfprint-device-DEBUG: Device reported deletion completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 297s # 297s # libfprint-device-DEBUG: Device reported close completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s ok 85 /driver/cancel/fail 297s # End of cancel tests 297s # Start of get_current_action tests 297s # libfprint-device-DEBUG: Device reported open completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 297s # 297s # libfprint-device-DEBUG: Device reported close completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s ok 86 /driver/get_current_action/open 297s # End of get_current_action tests 297s # Start of get_cancellable tests 297s ok 87 /driver/get_cancellable/error 297s # libfprint-device-DEBUG: Device reported open completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 297s # 297s # libfprint-device-DEBUG: Device reported close completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s ok 88 /driver/get_cancellable/open 297s # Start of open tests 297s # libfprint-device-DEBUG: Device reported open completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 297s # 297s # libfprint-device-DEBUG: Device reported close completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s ok 89 /driver/get_cancellable/open/internal 297s # End of open tests 297s # End of get_cancellable tests 297s # Start of action_is_cancelled tests 297s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 297s # libfprint-device-DEBUG: Tod version info is 'current' 297s # libfprint-device-DEBUG: Device reported open completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 297s # 297s # libfprint-device-DEBUG: Device reported close completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s ok 90 /driver/action_is_cancelled/open 297s ok 91 /driver/action_is_cancelled/error 297s # Start of open tests 297s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 297s # libfprint-device-DEBUG: Tod version info is 'current' 297s # libfprint-device-DEBUG: Device reported open completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 297s # 297s # libfprint-device-DEBUG: Device reported close completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s ok 92 /driver/action_is_cancelled/open/internal 297s # End of open tests 297s # End of action_is_cancelled tests 297s # Start of complete_action tests 297s # Start of all tests 297s ok 93 /driver/complete_action/all/error 297s # End of all tests 297s # End of complete_action tests 297s # Start of action_error tests 297s ok 94 /driver/action_error/error 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 297s # 297s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN 297s # libfprint-device-DEBUG: Device reported open completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 297s # 297s # libfprint-device-DEBUG: Device reported open completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 297s # 297s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL 297s # libfprint-device-DEBUG: Device reported enroll completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 297s # 297s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY 297s # libfprint-device-DEBUG: Device reported verify completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 297s # 297s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 297s # libfprint-device-DEBUG: Device reported identify completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 297s # 297s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE 297s # libfprint-device-DEBUG: Device reported capture completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 297s # 297s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST 297s # libfprint-device-DEBUG: Device reported listing completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 297s # 297s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE 297s # libfprint-device-DEBUG: Device reported deletion completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 297s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 297s # libfprint-device-DEBUG: Tod version info is 'current' 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 297s # 297s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLEAR_STORAGE 297s # libfprint-device-DEBUG: Device reported deletion completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 297s # 297s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE 297s # libfprint-device-DEBUG: Device reported close completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 297s ok 95 /driver/action_error/all 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 297s # 297s # libfprint-device-DEBUG: Device reported open completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 297s # 297s # libfprint-device-DEBUG: Device reported open completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 297s # 297s # libfprint-device-DEBUG: Device reported enroll completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 297s # 297s # libfprint-device-DEBUG: Device reported verify completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 297s # 297s # libfprint-device-DEBUG: Device reported identify completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 297s # 297s # libfprint-device-DEBUG: Device reported capture completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 297s # 297s # libfprint-device-DEBUG: Device reported listing completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 297s # 297s # libfprint-device-DEBUG: Device reported deletion completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 297s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 297s # libfprint-device-DEBUG: Tod version info is 'current' 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 297s # 297s # libfprint-device-DEBUG: Device reported deletion completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 297s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 297s # 297s # libfprint-device-DEBUG: Device reported close completion 297s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 297s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 297s ok 96 /driver/action_error/fail 297s # End of action_error tests 297s # Start of timeout tests 297s ok 97 /driver/timeout/cancelled 297s # End of timeout tests 297s # End of driver tests 297s PASS: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 297s Running test: libfprint-2/driver-aes3500.test 297s ** (umockdev-run:2151): DEBUG: 17:02:55.194: umockdev.vala:123: Created udev test bed /tmp/umockdev.74I9J2 297s ** (umockdev-run:2151): DEBUG: 17:02:55.194: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3/3-1/3-1.1/3-1.1.3 297s ** (umockdev-run:2151): DEBUG: 17:02:55.196: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3/3-1/3-1.1/3-1.1.3 (subsystem usb) 297s ** (umockdev-run:2151): DEBUG: 17:02:55.198: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.74I9J2/dev/bus/usb/003/004 297s ** (umockdev-run:2151): DEBUG: 17:02:55.198: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3/3-1/3-1.1 297s ** (umockdev-run:2151): DEBUG: 17:02:55.201: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3/3-1/3-1.1 (subsystem usb) 297s ** (umockdev-run:2151): DEBUG: 17:02:55.202: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.74I9J2/dev/bus/usb/003/003 297s ** (umockdev-run:2151): DEBUG: 17:02:55.203: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3/3-1 297s ** (umockdev-run:2151): DEBUG: 17:02:55.205: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3/3-1 (subsystem usb) 297s ** (umockdev-run:2151): DEBUG: 17:02:55.206: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.74I9J2/dev/bus/usb/003/002 297s ** (umockdev-run:2151): DEBUG: 17:02:55.207: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3 297s ** (umockdev-run:2151): DEBUG: 17:02:55.208: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3 (subsystem usb) 297s ** (umockdev-run:2151): DEBUG: 17:02:55.210: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.74I9J2/dev/bus/usb/003/001 297s ** (umockdev-run:2151): DEBUG: 17:02:55.210: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0 297s ** (umockdev-run:2151): DEBUG: 17:02:55.211: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0 (subsystem pci) 297s ** (umockdev-run:2151): DEBUG: 17:02:55.213: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0 297s ** (umockdev-run:2151): DEBUG: 17:02:55.214: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0 (subsystem pci) 297s ** (umockdev-run:2151): DEBUG: 17:02:55.216: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0 297s ** (umockdev-run:2151): DEBUG: 17:02:55.216: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0 (subsystem pci) 297s ** (umockdev-run:2151): DEBUG: 17:02:55.218: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.0 297s ** (umockdev-run:2151): DEBUG: 17:02:55.218: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.0 (subsystem pci) 297s (umockdev-run:2151): GLib-GIO-DEBUG: 17:02:55.220: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 297s (process:2155): libfprint-context-DEBUG: 17:02:55.266: Initializing FpContext (libfprint version 1.94.7+tod1) 297s (process:2155): libfprint-tod-DEBUG: 17:02:55.266: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 297s (process:2155): libfprint-context-DEBUG: 17:02:55.269: No driver found for USB device 2230:0006 297s (process:2155): libfprint-context-DEBUG: 17:02:55.269: No driver found for USB device 2230:0006 297s (process:2155): libfprint-context-DEBUG: 17:02:55.269: No driver found for USB device 1D6B:0002 297s (process:2155): libfprint-device-DEBUG: 17:02:55.269: Device reported probe completion 297s (process:2155): libfprint-device-DEBUG: 17:02:55.270: Completing action FPI_DEVICE_ACTION_PROBE in idle! 297s (process:2155): libfprint-device-DEBUG: 17:02:55.270: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find ha(process:2155): libfprint-image_device-DEBUG: 17:02:55.273: Image device open completed 297s (process:2155): libfprint-device-DEBUG: 17:02:55.273: Device reported open completion 297s (process:2155): libfprint-device-DEBUG: 17:02:55.273: Completing action FPI_DEVICE_ACTION_OPEN in idle! 297s (process:2155): libfprint-device-DEBUG: 17:02:55.273: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s (process:2155): libfprint-device-DEBUG: 17:02:55.273: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s (process:2155): libfprint-image_device-DEBUG: 17:02:55.273: Activating image device 297s (process:2155): libfprint-image_device-DEBUG: 17:02:55.273: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 297s (process:2155): libfprint-aeslib-DEBUG: 17:02:55.273: write 50 regs 297s (process:2155): libfprint-aeslib-DEBUG: 17:02:55.277: all registers written 297s ndle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s (process:2155): libfprint-image_device-DEBUG: 17:02:55.277: Image device activation completed 297s (process:2155): libfprint-image_device-DEBUG: 17:02:55.277: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 297s (process:2155): libfprint-image_device-DEBUG: 17:02:55.277: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 297s (process:2155): libfprint-aeslib-DEBUG: 17:02:55.277: write 6 regs 297s (process:2155): libfprint-device-DEBUG: 17:02:55.277: Device reported finger status change: FP_FINGER_STATUS_NEEDED 297s (process:2155): libfprint-aeslib-DEBUG: 17:02:55.278: all registers written 297s (process:2155): libfprint-device-DEBUG: 17:02:55.278: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 297s (process:2155): libfprint-image_device-DEBUG: 17:02:55.278: Image device reported finger status: on 297s (process:2155): libfprint-image_device-DEBUG: 17:02:55.278: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 297s (process:2155): libfprint-aes3k-DEBUG: 17:02:55.279: frame header byte e0 297s (process:2155): libfprint-aes3k-DEBUG: 17:02:55.279: frame header byte e1 297s (process:2155): libfprint-aes3k-DEBUG: 17:02:55.279: frame header byte e2 297s (process:2155): libfprint-aes3k-DEBUG: 17:02:55.279: frame header byte e3 297s (process:2155): libfprint-aes3k-DEBUG: 17:02:55.279: frame header byte e4 297s (process:2155): libfprint-aes3k-DEBUG: 17:02:55.279: frame header byte e5 297s (process:2155): libfprint-aes3k-DEBUG: 17:02:55.279: frame header byte e6 297s (process:2155): libfprint-aes3k-DEBUG: 17:02:55.279: frame header byte e7 297s (process:2155): libfprint-image_device-DEBUG: 17:02:55.279: Image device captured an image 297s (process:2155): libfprint-image_device-DEBUG: 17:02:55.283: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 297s (process:2155): libfprint-device-DEBUG: 17:02:55.283: Device reported finger status change: FP_FINGER_STATUS_PRESENT 297s (process:2155): libfprint-device-DEBUG: 17:02:55.283: Device reported finger status change: FP_FINGER_STATUS_NONE 297s (process:2155): libfprint-image_device-DEBUG: 17:02:55.283: Image device reported finger status: off 297s (process:2155): libfprint-image_device-DEBUG: 17:02:55.283: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 297s (process:2155): libfprint-image_device-DEBUG: 17:02:55.283: Deactivating image device 297s (process:2155): libfprint-image_device-DEBUG: 17:02:55.283: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 297s (process:2155): libfprint-image_device-DEBUG: 17:02:55.283: Image device deactivation completed 297s (process:2155): libfprint-image_device-DEBUG: 17:02:55.283: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 297s (process:2155): libfprint-image-DEBUG: 17:02:55.318: Minutiae scan completed in 0.038247 secs 297s (process:2155): libfprint-device-DEBUG: 17:02:55.318: Device reported capture completion 297s (process:2155): libfprint-device-DEBUG: 17:02:55.318: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 297s (process:2155): libfprint-device-DEBUG: 17:02:55.318: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 297s (process:2155): libfprint-image_device-DEBUG: 17:02:55.318: Image device close completed 297s (process:2155): libfprint-device-DEBUG: 17:02:55.318: Device reported close completion 297s (process:2155): libfprint-device-DEBUG: 17:02:55.318: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 297s (process:2155): libfprint-device-DEBUG: 17:02:55.319: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 297s ** (umockdev-run:2151): DEBUG: 17:02:55.408: umockdev.vala:150: Removing test bed /tmp/umockdev.74I9J2 297s (umockdev-run:2151): GLib-DEBUG: 17:02:55.416: unsetenv() is not thread-safe and should not be used after threads are created 297s Comparing PNGs /tmp/libfprint-umockdev-test-paf53ep3/capture.png and /usr/share/installed-tests/libfprint-2/aes3500/capture.png 297s PASS: libfprint-2/driver-aes3500.test 297s Running test: libfprint-2/driver-focaltech_moc.test 297s ** (umockdev-run:2164): DEBUG: 17:02:55.478: umockdev.vala:123: Created udev test bed /tmp/umockdev.XPUCK2 297s ** (umockdev-run:2164): DEBUG: 17:02:55.478: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1/3-1.4 297s ** (umockdev-run:2164): DEBUG: 17:02:55.482: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1/3-1.4 (subsystem usb) 297s ** (umockdev-run:2164): DEBUG: 17:02:55.484: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.XPUCK2/dev/bus/usb/003/006 297s ** (umockdev-run:2164): DEBUG: 17:02:55.484: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1 297s ** (umockdev-run:2164): DEBUG: 17:02:55.487: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1 (subsystem usb) 297s ** (umockdev-run:2164): DEBUG: 17:02:55.489: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.XPUCK2/dev/bus/usb/003/002 297s ** (umockdev-run:2164): DEBUG: 17:02:55.489: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3 297s ** (umockdev-run:2164): DEBUG: 17:02:55.493: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3 (subsystem usb) 297s ** (umockdev-run:2164): DEBUG: 17:02:55.494: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.XPUCK2/dev/bus/usb/003/001 297s ** (umockdev-run:2164): DEBUG: 17:02:55.494: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0 297s ** (umockdev-run:2164): DEBUG: 17:02:55.496: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0 (subsystem pci) 297s ** (umockdev-run:2164): DEBUG: 17:02:55.498: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1c.4 297s ** (umockdev-run:2164): DEBUG: 17:02:55.499: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1c.4 (subsystem pci) 297s (process:2168): libfprint-context-DEBUG: 17:02:55.543: Initializing FpContext (libfprint version 1.94.7+tod1) 297s (process:2168): libfprint-tod-DEBUG: 17:02:55.543: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 297s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:55.545: 131530868: ../libfprint/drivers/focaltech_moc/focaltech_moc.c:1849 297s (process:2168): libfprint-context-DEBUG: 17:02:55.546: No driver found for USB device 05E3:0608 297s (process:2168): libfprint-context-DEBUG: 17:02:55.546: No driver found for USB device 1D6B:0002 297s (process:2168): libfprint-device-DEBUG: 17:02:55.546: Device reported probe completion 297s (process:2168): libfprint-device-DEBUG: 17:02:55.546: Completing action FPI_DEVICE_ACTION_PROBE in idle! 297s (process:2168): libfprint-device-DEBUG: 17:02:55.546: Not updating temperature model, device can run continuously! 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find ha(process:2168): libfprint-focaltech_moc-DEBUG: 17:02:55.549: class:dc, subclass:a0, protocol:b0 297s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:55.549: bytes size:0 297s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:55.549: 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 297s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:55.549: bytes size:0 297s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:55.549: 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 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.549: [focaltech_moc] DEV_INIT_STATES entering state 0 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.550: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.550: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 297s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:55.550: focaltechmoc enroll_times: 10 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.550: [focaltech_moc] DEV_INIT_STATES entering state 1 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.550: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.551: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.551: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.551: [focaltech_moc] DEV_INIT_STATES completed successfully 297s (process:2168): libfprint-device-DEBUG: 17:02:55.551: Device reported open completion 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.551: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 297s (process:2168): libfprint-device-DEBUG: 17:02:55.551: Completing action FPI_DEVICE_ACTION_OPEN in idle! 297s (process:2168): libfprint-device-DEBUG: 17:02:55.552: Not updating temperature model, device can run continuously! 297s (process:2168): libfprint-device-DEBUG: 17:02:55.552: Not updating temperature model, device can run continuously! 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.552: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 0 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.552: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.553: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.553: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 1 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.553: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.553: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.554: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.554: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 2 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.554: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.554: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.555: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.555: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 3 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.555: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.555: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.556: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 297s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:55.556: focaltechmoc user id: FP1-00000000-0-00000000-nobody 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.556: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.556: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.556: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.557: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.557: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.557: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.607: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.607: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.608: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.608: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.608: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.658: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.658: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.659: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.659: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.659: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.709: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.709: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.710: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.710: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.710: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 297s ndle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: error [op_handle_events] cannot find handle for fd 9 297s libusb: warning [read_sysfs_attr] attribute bConfigurationValue doesn't end with newline? 297s libusb: warning [read_sysfs_attr] attribute bConfigurationValue doesn't end with newline? 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.760: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.760: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.761: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.761: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.761: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.811: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.811: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.812: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.812: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.812: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.862: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.862: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.863: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.863: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.863: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.864: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.864: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 297s (process:2168): libfprint-device-DEBUG: 17:02:55.864: Device reported enroll progress, reported 1 of 10 have been completed 297s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:55.864: focaltechmoc remain: 9 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.864: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.864: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.865: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.865: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.865: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.866: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.916: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.916: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.916: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.916: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.916: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.967: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.967: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 297s (process:2168): libfprint-SSM-DEBUG: 17:02:55.967: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:55.968: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 298s (process:2168): libfprint-SSM-DEBUG: 17:02:55.968: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s Executing: libfprint-2/driver-focaltech_moc.test 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.018: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.018: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.018: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.019: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.019: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.069: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.069: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.069: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.070: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.070: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.120: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.120: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.121: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.121: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.121: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.121: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.121: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-device-DEBUG: 17:02:56.122: Device reported enroll progress, reported 2 of 10 have been completed 298s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:56.122: focaltechmoc remain: 8 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.122: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.122: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.122: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.123: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.123: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.123: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.173: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.173: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.174: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.174: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.174: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.175: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.175: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-device-DEBUG: 17:02:56.175: Device reported enroll progress, reported 3 of 10 have been completed 298s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:56.175: focaltechmoc remain: 7 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.175: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.175: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.176: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.176: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.176: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.176: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.227: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.227: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.227: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.228: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.228: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.278: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.278: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.278: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.279: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.279: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.329: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.329: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.329: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.330: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.330: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.380: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.380: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.380: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.381: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.381: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.431: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.431: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.432: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.432: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.432: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.432: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.432: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-device-DEBUG: 17:02:56.433: Device reported enroll progress, reported 4 of 10 have been completed 298s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:56.433: focaltechmoc remain: 6 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.433: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.433: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.433: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.433: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.434: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.434: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.484: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.484: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.485: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.485: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.485: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.535: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.535: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.536: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.536: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.536: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.586: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.586: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.587: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.587: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.587: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.588: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.588: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-device-DEBUG: 17:02:56.588: Device reported enroll progress, reported 5 of 10 have been completed 298s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:56.588: focaltechmoc remain: 5 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.588: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.588: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.589: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.589: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.589: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.589: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.640: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.640: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.640: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.640: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.640: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.691: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.691: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.691: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.692: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.692: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.742: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.742: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.742: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.743: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.743: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.793: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.793: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.793: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.794: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.794: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.794: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.795: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-device-DEBUG: 17:02:56.795: Device reported enroll progress, reported 6 of 10 have been completed 298s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:56.795: focaltechmoc remain: 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.795: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.795: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.795: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.796: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.796: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.796: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.796: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.797: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-device-DEBUG: 17:02:56.797: Device reported enroll progress, reported 6 of 10 have been completed 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.797: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.797: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.797: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.797: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.798: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.798: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.848: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.848: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.849: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.849: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.849: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.899: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.899: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.900: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.900: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.900: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.950: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.950: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.951: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.951: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 298s (process:2168): libfprint-SSM-DEBUG: 17:02:56.951: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.001: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.001: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.002: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.002: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.002: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.003: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.003: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-device-DEBUG: 17:02:57.003: Device reported enroll progress, reported 7 of 10 have been completed 299s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:57.004: focaltechmoc remain: 3 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.004: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.004: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.004: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.004: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.005: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.005: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.055: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.055: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.055: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.055: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.055: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.106: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.106: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.106: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.107: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.107: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.107: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.107: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-device-DEBUG: 17:02:57.107: Device reported enroll progress, reported 8 of 10 have been completed 299s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:57.108: focaltechmoc remain: 2 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.108: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.108: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.108: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.108: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.109: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.109: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.159: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.159: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.159: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.160: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.160: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.160: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.160: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-device-DEBUG: 17:02:57.160: Device reported enroll progress, reported 9 of 10 have been completed 299s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:57.161: focaltechmoc remain: 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.161: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.161: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.161: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.161: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.161: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.161: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.212: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.212: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.212: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.213: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.213: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.213: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.213: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-device-DEBUG: 17:02:57.213: Device reported enroll progress, reported 10 of 10 have been completed 299s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:57.214: focaltechmoc remain: 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.214: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 7 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.214: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.214: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.214: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.214: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 8 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.215: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.215: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.215: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:57.216: focaltech_moc_commit_cb success 299s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:57.216: Enrollment was successful! 299s (process:2168): libfprint-device-DEBUG: 17:02:57.216: Device reported enroll completion 299s (process:2168): libfprint-device-DEBUG: 17:02:57.216: Print for finger FP_FINGER_UNKNOWN enrolled 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.216: [focaltech_moc] MOC_ENROLL_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.216: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-device-DEBUG: 17:02:57.216: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 299s (process:2168): libfprint-device-DEBUG: 17:02:57.216: Not updating temperature model, device can run continuously! 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.216: [focaltech_moc] MOC_LIST_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.216: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.216: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.217: [focaltech_moc] MOC_LIST_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.217: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.217: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.217: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:57.218: focaltechmoc add slot: 0 299s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:57.218: FP1-00000000-0-00000000-nobody 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.218: [focaltech_moc] MOC_LIST_NUM_STATES entering state 2 299s (process:2168): libfprint-device-DEBUG: 17:02:57.218: Device reported listing completion 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.218: [focaltech_moc] MOC_LIST_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.218: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-device-DEBUG: 17:02:57.218: Completing action FPI_DEVICE_ACTION_LIST in idle! 299s (process:2168): libfprint-device-DEBUG: 17:02:57.218: Not updating temperature model, device can run continuously! 299s (process:2168): libfprint-device-DEBUG: 17:02:57.218: Not updating temperature model, device can run continuously! 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.218: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.218: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.218: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.219: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.219: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.219: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.219: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.220: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.220: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.270: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.270: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.270: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.271: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.271: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.321: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.321: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.321: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.322: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.322: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.372: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.372: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.373: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.373: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.373: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.423: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.423: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.424: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.424: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 3 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.424: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.424: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.425: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.425: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 4 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.425: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.426: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.426: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-device-DEBUG: 17:02:57.426: Device reported verify result 299s (process:2168): libfprint-device-DEBUG: 17:02:57.426: Device reported verify completion 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.426: [focaltech_moc] MOC_IDENTIFY_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.426: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-device-DEBUG: 17:02:57.426: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 299s (process:2168): libfprint-device-DEBUG: 17:02:57.426: Not updating temperature model, device can run continuously! 299s (process:2168): libfprint-device-DEBUG: 17:02:57.427: Not updating temperature model, device can run continuously! 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.427: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.427: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.428: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.428: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.428: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.429: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.429: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.429: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.429: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.479: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.479: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.480: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.480: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.480: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.530: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.530: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.531: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.531: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 3 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.531: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.532: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.532: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.532: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 4 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.532: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.533: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.533: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-device-DEBUG: 17:02:57.533: Device reported identify result 299s (process:2168): libfprint-device-DEBUG: 17:02:57.533: Device reported identify completion 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.533: [focaltech_moc] MOC_IDENTIFY_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.533: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-device-DEBUG: 17:02:57.533: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 299s (process:2168): libfprint-device-DEBUG: 17:02:57.533: Not updating temperature model, device can run continuously! 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.534: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.534: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.534: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.535: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.535: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.535: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.535: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:57.536: focaltechmoc add slot: 0 299s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:57.536: FP1-00000000-0-00000000-nobody 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.536: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 2 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.536: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.536: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.536: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.537: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 3 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.537: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.537: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.537: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 299s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:57.538: delete slot 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.538: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 3 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.538: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 4 299s (process:2168): libfprint-device-DEBUG: 17:02:57.538: Device reported deletion completion 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.538: [focaltech_moc] MOC_DELETE_NUM_STATES completed successfully 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.538: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 299s (process:2168): libfprint-device-DEBUG: 17:02:57.538: Completing action FPI_DEVICE_ACTION_DELETE in idle! 299s (process:2168): libfprint-device-DEBUG: 17:02:57.538: Not updating temperature model, device can run continuously! 299s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:57.538: Focaltechmoc dev_exit 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.538: [focaltech_moc] DEV_EXIT_STATES entering state 0 299s (process:2168): libfprint-SSM-DEBUG: 17:02:57.538: [focaltech_moc] DEV_EXIT_STATES completed successfully 299s (process:2168): libfprint-focaltech_moc-DEBUG: 17:02:57.538: class:dc, subclass:a0, protocol:b0 299s (process:2168): libfprint-device-DEBUG: 17:02:57.538: Device reported close completion 299s (process:2168): libfprint-device-DEBUG: 17:02:57.538: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 299s (process:2168): libfprint-device-DEBUG: 17:02:57.538: Not updating temperature model, device can run continuously! 299s enrolling 299s finger status: 299s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xe23a451cb680 (FpiDeviceFocaltechMoc at 0x2c46e100)>, 1, None, None, None) 299s finger status: 299s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xe23a451cb680 (FpiDeviceFocaltechMoc at 0x2c46e100)>, 2, None, None, None) 299s finger status: 299s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xe23a451cb680 (FpiDeviceFocaltechMoc at 0x2c46e100)>, 3, None, None, None) 299s finger status: 299s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xe23a451cb680 (FpiDeviceFocaltechMoc at 0x2c46e100)>, 4, None, None, None) 299s finger status: 299s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xe23a451cb680 (FpiDeviceFocaltechMoc at 0x2c46e100)>, 5, None, None, None) 299s finger status: 299s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xe23a451cb680 (FpiDeviceFocaltechMoc at 0x2c46e100)>, 6, None, None, None) 299s finger status: 299s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xe23a451cb680 (FpiDeviceFocaltechMoc at 0x2c46e100)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 299s finger status: 299s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xe23a451cb680 (FpiDeviceFocaltechMoc at 0x2c46e100)>, 7, None, None, None) 299s finger status: 299s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xe23a451cb680 (FpiDeviceFocaltechMoc at 0x2c46e100)>, 8, None, None, None) 299s finger status: 299s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xe23a451cb680 (FpiDeviceFocaltechMoc at 0x2c46e100)>, 9, None, None, None) 299s finger status: 299s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xe23a451cb680 (FpiDeviceFocaltechMoc at 0x2c46e100)>, 10, None, None, None) 299s enroll done 299s listing 299s listing done 299s verifying 299s verify done 299s async identifying 299s indentification_done: 299s deleting 299s delete done 299s ** (umockdev-run:2164): DEBUG: 17:02:57.549: umockdev.vala:150: Removing test bed /tmp/umockdev.XPUCK2 299s (umockdev-run:2164): GLib-DEBUG: 17:02:57.554: unsetenv() is not thread-safe and should not be used after threads are created 299s PASS: libfprint-2/driver-focaltech_moc.test 299s Running test: libfprint-2/virtual-image.test 299s (process:2174): libfprint-context-DEBUG: 17:02:57.629: Initializing FpContext (libfprint version 1.94.7+tod1) 299s (process:2174): libfprint-tod-DEBUG: 17:02:57.629: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 299s (process:2174): libfprint-context-DEBUG: 17:02:57.630: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-fz2akmx4/virtual-image.socket 299s (process:2174): libfprint-context-DEBUG: 17:02:57.630: created 299s (process:2174): libfprint-device-DEBUG: 17:02:57.630: Device reported probe completion 299s (process:2174): libfprint-device-DEBUG: 17:02:57.630: Completing action FPI_DEVICE_ACTION_PROBE in idle! 299s (process:2174): libfprint-device-DEBUG: 17:02:57.630: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 299s test_capture_prevents_close (__main__.VirtualImage.test_capture_prevents_close) ... (process:2174): libfprint-virtual_image-DEBUG: 17:02:57.635: 133620260: ../libfprint/drivers/virtual-image.c:216 299s (process:2174): libfprint-virtual_device_connection-DEBUG: 17:02:57.635: 133620352: ../libfprint/drivers/virtual-device-listener.c:153 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.735: Image device open completed 299s (process:2174): libfprint-device-DEBUG: 17:02:57.735: Device reported open completion 299s (process:2174): libfprint-device-DEBUG: 17:02:57.735: Completing action FPI_DEVICE_ACTION_OPEN in idle! 299s (process:2174): libfprint-device-DEBUG: 17:02:57.735: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 299s (process:2174): libfprint-device-DEBUG: 17:02:57.736: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.736: Activating image device 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.736: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.736: Image device activation completed 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.736: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.736: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 299s (process:2174): libfprint-device-DEBUG: 17:02:57.736: Device reported finger status change: FP_FINGER_STATUS_NEEDED 299s (process:2174): libfprint-virtual_device_connection-DEBUG: 17:02:57.736: Got a new connection! 299s (process:2174): libfprint-device-DEBUG: 17:02:57.737: Idle cancelling on ongoing operation! 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.737: Deactivating image device 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.737: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.737: Image device deactivation completed 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.737: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 299s (process:2174): libfprint-device-DEBUG: 17:02:57.737: Device reported generic error (Operation was cancelled) during action; action was: FPI_DEVICE_ACTION_CAPTURE 299s (process:2174): libfprint-device-DEBUG: 17:02:57.737: Device reported capture completion 299s (process:2174): libfprint-device-DEBUG: 17:02:57.737: Device reported finger status change: FP_FINGER_STATUS_NONE 299s (process:2174): libfprint-device-DEBUG: 17:02:57.737: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 299s (process:2174): libfprint-device-DEBUG: 17:02:57.737: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 299s (process:2174): libfprint-virtual_image-DEBUG: 17:02:57.739: 133724643: ../libfprint/drivers/virtual-image.c:244 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.840: Image device close completed 299s (process:2174): libfprint-device-DEBUG: 17:02:57.840: Device reported close completion 299s (process:2174): libfprint-device-DEBUG: 17:02:57.840: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 299s (process:2174): libfprint-device-DEBUG: 17:02:57.840: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 299s Capture operation finished 299s Capture cancelled as expected 299s ok 299s test_enroll_verify (__main__.VirtualImage.test_enroll_verify) ... (process:2174): libfprint-virtual_image-DEBUG: 17:02:57.840: 133825364: ../libfprint/drivers/virtual-image.c:216 299s (process:2174): libfprint-virtual_device_connection-DEBUG: 17:02:57.840: 133825376: ../libfprint/drivers/virtual-device-listener.c:153 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.940: Image device open completed 299s (process:2174): libfprint-device-DEBUG: 17:02:57.940: Device reported open completion 299s (process:2174): libfprint-device-DEBUG: 17:02:57.940: Completing action FPI_DEVICE_ACTION_OPEN in idle! 299s (process:2174): libfprint-device-DEBUG: 17:02:57.940: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 299s (process:2174): libfprint-device-DEBUG: 17:02:57.942: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.942: Activating image device 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.942: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.942: Image device activation completed 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.942: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.942: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 299s (process:2174): libfprint-device-DEBUG: 17:02:57.942: Device reported finger status change: FP_FINGER_STATUS_NEEDED 299s (process:2174): libfprint-virtual_device_connection-DEBUG: 17:02:57.944: Got a new connection! 299s (process:2174): libfprint-virtual_image-DEBUG: 17:02:57.944: image data: 0x15cdcd40 299s (process:2174): libfprint-device-DEBUG: 17:02:57.944: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.944: Image device reported finger status: on 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.944: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.944: Image device captured an image 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.944: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 299s (process:2174): libfprint-device-DEBUG: 17:02:57.944: Device reported finger status change: FP_FINGER_STATUS_PRESENT 299s (process:2174): libfprint-device-DEBUG: 17:02:57.947: Device reported finger status change: FP_FINGER_STATUS_NONE 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.947: Image device reported finger status: off 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.947: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 299s (process:2174): libfprint-image-DEBUG: 17:02:57.968: Minutiae scan completed in 0.023038 secs 299s (process:2174): libfprint-device-DEBUG: 17:02:57.968: Device reported enroll progress, reported 1 of 5 have been completed 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.968: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 299s (process:2174): libfprint-device-DEBUG: 17:02:57.968: Device reported finger status change: FP_FINGER_STATUS_NEEDED 299s (process:2174): libfprint-device-DEBUG: 17:02:57.968: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.968: Image device reported finger status: on 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.968: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 299s (process:2174): libfprint-virtual_image-DEBUG: 17:02:57.968: image data: 0x15cf9e30 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.968: Image device captured an image 299s (process:2174): libfprint-image_device-DEBUG: 17:02:57.968: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 299s (process:2174): libfprint-device-DEBUG: 17:02:57.968: Device reported finger status change: FP_FINGER_STATUS_PRESENT 300s (process:2174): libfprint-image-DEBUG: 17:02:57.991: Minutiae scan completed in 0.022913 secs 300s (process:2174): libfprint-device-DEBUG: 17:02:57.991: Device reported enroll progress, reported 2 of 5 have been completed 300s (process:2174): libfprint-device-DEBUG: 17:02:57.991: Device reported finger status change: FP_FINGER_STATUS_NONE 300s (process:2174): libfprint-image_device-DEBUG: 17:02:57.991: Image device reported finger status: off 300s (process:2174): libfprint-image_device-DEBUG: 17:02:57.991: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 300s (process:2174): libfprint-image_device-DEBUG: 17:02:57.991: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 300s (process:2174): libfprint-device-DEBUG: 17:02:57.991: Device reported finger status change: FP_FINGER_STATUS_NEEDED 300s (process:2174): libfprint-virtual_image-DEBUG: 17:02:57.992: image data: 0x15cde990 300s (process:2174): libfprint-device-DEBUG: 17:02:57.992: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 300s (process:2174): libfprint-image_device-DEBUG: 17:02:57.992: Image device reported finger status: on 300s (process:2174): libfprint-image_device-DEBUG: 17:02:57.992: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 300s (process:2174): libfprint-image_device-DEBUG: 17:02:57.992: Image device captured an image 300s (process:2174): libfprint-image_device-DEBUG: 17:02:57.995: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 300s (process:2174): libfprint-device-DEBUG: 17:02:57.995: Device reported finger status change: FP_FINGER_STATUS_PRESENT 300s (process:2174): libfprint-device-DEBUG: 17:02:57.995: Device reported finger status change: FP_FINGER_STATUS_NONE 300s (process:2174): libfprint-image_device-DEBUG: 17:02:57.995: Image device reported finger status: off 300s (process:2174): libfprint-image_device-DEBUG: 17:02:57.995: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 300s (process:2174): libfprint-image-DEBUG: 17:02:58.015: Minutiae scan completed in 0.023124 secs 300s (process:2174): libfprint-device-DEBUG: 17:02:58.015: Device reported enroll progress, reported 3 of 5 have been completed 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.015: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 300s (process:2174): libfprint-device-DEBUG: 17:02:58.015: Device reported finger status change: FP_FINGER_STATUS_NEEDED 300s (process:2174): libfprint-virtual_image-DEBUG: 17:02:58.015: image data: 0x15cfba80 300s (process:2174): libfprint-device-DEBUG: 17:02:58.015: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.015: Image device reported finger status: on 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.015: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.015: Image device captured an image 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.015: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 300s (process:2174): libfprint-device-DEBUG: 17:02:58.015: Device reported finger status change: FP_FINGER_STATUS_PRESENT 300s (process:2174): libfprint-device-DEBUG: 17:02:58.015: Device reported finger status change: FP_FINGER_STATUS_NONE 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.015: Image device reported finger status: off 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.015: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 300s (process:2174): libfprint-image-DEBUG: 17:02:58.038: Minutiae scan completed in 0.022837 secs 300s (process:2174): libfprint-device-DEBUG: 17:02:58.038: Device reported enroll progress, reported 4 of 5 have been completed 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.038: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 300s (process:2174): libfprint-device-DEBUG: 17:02:58.038: Device reported finger status change: FP_FINGER_STATUS_NEEDED 300s (process:2174): libfprint-virtual_image-DEBUG: 17:02:58.038: image data: 0x15cdfc70 300s (process:2174): libfprint-device-DEBUG: 17:02:58.038: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.039: Image device reported finger status: on 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.039: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.039: Image device captured an image 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.043: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 300s (process:2174): libfprint-device-DEBUG: 17:02:58.043: Device reported finger status change: FP_FINGER_STATUS_PRESENT 300s (process:2174): libfprint-device-DEBUG: 17:02:58.043: Device reported finger status change: FP_FINGER_STATUS_NONE 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.043: Image device reported finger status: off 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.043: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 300s (process:2174): libfprint-image-DEBUG: 17:02:58.061: Minutiae scan completed in 0.022867 secs 300s (process:2174): libfprint-device-DEBUG: 17:02:58.062: Device reported enroll progress, reported 5 of 5 have been completed 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.062: Deactivating image device 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.062: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.062: Image device deactivation completed 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.062: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 300s (process:2174): libfprint-device-DEBUG: 17:02:58.062: Device reported enroll completion 300s (process:2174): libfprint-device-DEBUG: 17:02:58.062: Print for finger FP_FINGER_LEFT_THUMB enrolled 300s (process:2174): libfprint-device-DEBUG: 17:02:58.062: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 300s (process:2174): libfprint-device-DEBUG: 17:02:58.062: Updated temperature model after 0.12 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 300s (process:2174): libfprint-device-DEBUG: 17:02:58.062: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.062: Activating image device 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.062: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.062: Image device activation completed 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.062: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.062: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 300s (process:2174): libfprint-device-DEBUG: 17:02:58.062: Device reported finger status change: FP_FINGER_STATUS_NEEDED 300s (process:2174): libfprint-virtual_image-DEBUG: 17:02:58.062: image data: 0x15cfcd60 300s (process:2174): libfprint-device-DEBUG: 17:02:58.062: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.062: Image device reported finger status: on 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.062: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.062: Image device captured an image 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.067: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 300s (process:2174): libfprint-device-DEBUG: 17:02:58.067: Device reported finger status change: FP_FINGER_STATUS_PRESENT 300s (process:2174): libfprint-device-DEBUG: 17:02:58.067: Device reported finger status change: FP_FINGER_STATUS_NONE 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.067: Image device reported finger status: off 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.067: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.067: Deactivating image device 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.067: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.067: Image device deactivation completed 300s (process:2174): libfprint-image_device-DEBUG: 17:02:58.067: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 300s (process:2174): libfprint-image-DEBUG: 17:02:58.085: Minutiae scan completed in 0.022844 secs 301s (process:2174): libfprint-print-DEBUG: 17:02:59.039: score 1093/40 301s (process:2174): libfprint-device-DEBUG: 17:02:59.039: Device reported verify result 301s (process:2174): libfprint-device-DEBUG: 17:02:59.039: Device reported verify completion 301s (process:2174): libfprint-device-DEBUG: 17:02:59.040: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 301s (process:2174): libfprint-device-DEBUG: 17:02:59.040: Updated temperature model after 0.98 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2174): libfprint-device-DEBUG: 17:02:59.040: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.040: Activating image device 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.040: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.040: Image device activation completed 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.040: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.040: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 301s (process:2174): libfprint-device-DEBUG: 17:02:59.040: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2174): libfprint-virtual_image-DEBUG: 17:02:59.040: image data: 0x15cf37b0 301s (process:2174): libfprint-device-DEBUG: 17:02:59.040: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.040: Image device reported finger status: on 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.040: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.041: Image device captured an image 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.043: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 301s (process:2174): libfprint-device-DEBUG: 17:02:59.043: Device reported finger status change: FP_FINGER_STATUS_PRESENT 301s (process:2174): libfprint-device-DEBUG: 17:02:59.043: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.043: Image device reported finger status: off 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.043: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.043: Deactivating image device 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.043: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.043: Image device deactivation completed 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.043: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 301s (process:2174): libfprint-image-DEBUG: 17:02:59.061: Minutiae scan completed in 0.020618 secs 301s (process:2174): libfprint-print-DEBUG: 17:02:59.067: score 10/40 301s (process:2174): libfprint-print-DEBUG: 17:02:59.073: score 10/40 301s (process:2174): libfprint-print-DEBUG: 17:02:59.078: score 10/40 301s (process:2174): libfprint-print-DEBUG: 17:02:59.084: score 10/40 301s (process:2174): libfprint-print-DEBUG: 17:02:59.089: score 10/40 301s (process:2174): libfprint-device-DEBUG: 17:02:59.089: Device reported verify result 301s (process:2174): libfprint-device-DEBUG: 17:02:59.089: Device reported verify completion 301s (process:2174): libfprint-device-DEBUG: 17:02:59.089: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 301s (process:2174): libfprint-device-DEBUG: 17:02:59.089: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2174): libfprint-device-DEBUG: 17:02:59.089: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.089: Activating image device 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.089: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.089: Image device activation completed 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.089: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.089: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 301s (process:2174): libfprint-device-DEBUG: 17:02:59.090: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2174): libfprint-virtual_image-DEBUG: 17:02:59.090: image data: 0x15d027c0 301s (process:2174): libfprint-device-DEBUG: 17:02:59.090: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.090: Image device reported finger status: on 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.090: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.090: Image device captured an image 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.095: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 301s (process:2174): libfprint-device-DEBUG: 17:02:59.095: Device reported finger status change: FP_FINGER_STATUS_PRESENT 301s (process:2174): libfprint-device-DEBUG: 17:02:59.095: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.095: Image device reported finger status: off 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.095: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 301s (process:2174): libfprint-image-DEBUG: 17:02:59.111: Minutiae scan completed in 0.020609 secs 301s (process:2174): libfprint-device-DEBUG: 17:02:59.111: Device reported enroll progress, reported 1 of 5 have been completed 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.111: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 301s (process:2174): libfprint-device-DEBUG: 17:02:59.111: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2174): libfprint-device-DEBUG: 17:02:59.111: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.111: Image device reported finger status: on 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.111: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 301s (process:2174): libfprint-virtual_image-DEBUG: 17:02:59.111: image data: 0x15d117d0 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.111: Image device captured an image 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.111: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 301s (process:2174): libfprint-device-DEBUG: 17:02:59.111: Device reported finger status change: FP_FINGER_STATUS_PRESENT 301s (process:2174): libfprint-image-DEBUG: 17:02:59.132: Minutiae scan completed in 0.020463 secs 301s (process:2174): libfprint-device-DEBUG: 17:02:59.132: Device reported enroll progress, reported 2 of 5 have been completed 301s (process:2174): libfprint-device-DEBUG: 17:02:59.132: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.132: Image device reported finger status: off 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.132: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.132: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 301s (process:2174): libfprint-device-DEBUG: 17:02:59.132: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2174): libfprint-virtual_image-DEBUG: 17:02:59.132: image data: 0x15d027c0 301s (process:2174): libfprint-device-DEBUG: 17:02:59.132: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.132: Image device reported finger status: on 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.132: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.132: Image device captured an image 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.132: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 301s (process:2174): libfprint-device-DEBUG: 17:02:59.132: Device reported finger status change: FP_FINGER_STATUS_PRESENT 301s (process:2174): libfprint-device-DEBUG: 17:02:59.132: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.132: Image device reported finger status: off 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.132: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 301s (process:2174): libfprint-image-DEBUG: 17:02:59.153: Minutiae scan completed in 0.020392 secs 301s (process:2174): libfprint-device-DEBUG: 17:02:59.153: Device reported enroll progress, reported 3 of 5 have been completed 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.153: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 301s (process:2174): libfprint-device-DEBUG: 17:02:59.153: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2174): libfprint-virtual_image-DEBUG: 17:02:59.153: image data: 0x15d117d0 301s (process:2174): libfprint-device-DEBUG: 17:02:59.153: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.153: Image device reported finger status: on 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.153: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.153: Image device captured an image 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.159: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 301s (process:2174): libfprint-device-DEBUG: 17:02:59.159: Device reported finger status change: FP_FINGER_STATUS_PRESENT 301s (process:2174): libfprint-device-DEBUG: 17:02:59.159: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.159: Image device reported finger status: off 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.159: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 301s (process:2174): libfprint-image-DEBUG: 17:02:59.173: Minutiae scan completed in 0.020538 secs 301s (process:2174): libfprint-device-DEBUG: 17:02:59.174: Device reported enroll progress, reported 4 of 5 have been completed 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.174: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 301s (process:2174): libfprint-device-DEBUG: 17:02:59.174: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2174): libfprint-virtual_image-DEBUG: 17:02:59.174: image data: 0x15d027c0 301s (process:2174): libfprint-device-DEBUG: 17:02:59.174: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.174: Image device reported finger status: on 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.174: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.174: Image device captured an image 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.174: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 301s (process:2174): libfprint-device-DEBUG: 17:02:59.174: Device reported finger status change: FP_FINGER_STATUS_PRESENT 301s (process:2174): libfprint-device-DEBUG: 17:02:59.174: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.174: Image device reported finger status: off 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.174: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 301s (process:2174): libfprint-image-DEBUG: 17:02:59.194: Minutiae scan completed in 0.020424 secs 301s (process:2174): libfprint-device-DEBUG: 17:02:59.194: Device reported enroll progress, reported 5 of 5 have been completed 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.194: Deactivating image device 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.194: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.194: Image device deactivation completed 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.194: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 301s (process:2174): libfprint-device-DEBUG: 17:02:59.194: Device reported enroll completion 301s (process:2174): libfprint-device-DEBUG: 17:02:59.194: Print for finger FP_FINGER_LEFT_THUMB enrolled 301s (process:2174): libfprint-device-DEBUG: 17:02:59.194: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 301s (process:2174): libfprint-device-DEBUG: 17:02:59.194: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2174): libfprint-device-DEBUG: 17:02:59.195: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.195: Activating image device 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.195: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.195: Image device activation completed 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.195: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.195: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 301s (process:2174): libfprint-device-DEBUG: 17:02:59.195: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2174): libfprint-virtual_image-DEBUG: 17:02:59.195: image data: 0x15cf2760 301s (process:2174): libfprint-device-DEBUG: 17:02:59.195: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.195: Image device reported finger status: on 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.195: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.195: Image device captured an image 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.195: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 301s (process:2174): libfprint-device-DEBUG: 17:02:59.195: Device reported finger status change: FP_FINGER_STATUS_PRESENT 301s (process:2174): libfprint-device-DEBUG: 17:02:59.195: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.195: Image device reported finger status: off 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.195: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.195: Deactivating image device 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.195: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.195: Image device deactivation completed 301s (process:2174): libfprint-image_device-DEBUG: 17:02:59.195: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 301s (process:2174): libfprint-image-DEBUG: 17:02:59.218: Minutiae scan completed in 0.022724 secs 302s (process:2174): libfprint-print-DEBUG: 17:03:00.167: score 1093/40 302s (process:2174): libfprint-device-DEBUG: 17:03:00.167: Device reported verify result 302s (process:2174): libfprint-device-DEBUG: 17:03:00.167: Device reported verify completion 302s (process:2174): libfprint-device-DEBUG: 17:03:00.167: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 302s (process:2174): libfprint-device-DEBUG: 17:03:00.167: Updated temperature model after 0.97 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 302s (process:2174): libfprint-device-DEBUG: 17:03:00.167: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.167: Activating image device 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.167: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.168: Image device activation completed 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.168: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.168: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 302s (process:2174): libfprint-device-DEBUG: 17:03:00.168: Device reported finger status change: FP_FINGER_STATUS_NEEDED 302s (process:2174): libfprint-virtual_image-DEBUG: 17:03:00.168: image data: 0x15cf36c0 302s (process:2174): libfprint-device-DEBUG: 17:03:00.168: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.168: Image device reported finger status: on 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.168: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.168: Image device captured an image 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.171: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 302s (process:2174): libfprint-device-DEBUG: 17:03:00.171: Device reported finger status change: FP_FINGER_STATUS_PRESENT 302s (process:2174): libfprint-device-DEBUG: 17:03:00.171: Device reported finger status change: FP_FINGER_STATUS_NONE 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.171: Image device reported finger status: off 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.171: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.171: Deactivating image device 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.171: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.171: Image device deactivation completed 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.171: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 302s (process:2174): libfprint-image-DEBUG: 17:03:00.189: Minutiae scan completed in 0.020604 secs 302s (process:2174): libfprint-print-DEBUG: 17:03:00.195: score 10/40 302s (process:2174): libfprint-print-DEBUG: 17:03:00.200: score 10/40 302s (process:2174): libfprint-print-DEBUG: 17:03:00.206: score 10/40 302s (process:2174): libfprint-print-DEBUG: 17:03:00.211: score 10/40 302s (process:2174): libfprint-print-DEBUG: 17:03:00.217: score 10/40 302s (process:2174): libfprint-print-DEBUG: 17:03:00.409: score 855/40 302s (process:2174): libfprint-device-DEBUG: 17:03:00.409: Device reported verify result 302s (process:2174): libfprint-device-DEBUG: 17:03:00.409: Device reported verify completion 302s (process:2174): libfprint-device-DEBUG: 17:03:00.410: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 302s (process:2174): libfprint-device-DEBUG: 17:03:00.410: Updated temperature model after 0.24 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 302s (process:2174): libfprint-device-DEBUG: 17:03:00.410: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.410: Activating image device 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.410: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.410: Image device activation completed 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.410: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.410: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 302s (process:2174): libfprint-device-DEBUG: 17:03:00.410: Device reported finger status change: FP_FINGER_STATUS_NEEDED 302s (process:2174): libfprint-device-DEBUG: 17:03:00.410: Device reported verify result 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.410: Deactivating image device 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.411: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.411: Image device deactivation completed 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.411: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 302s (process:2174): libfprint-device-DEBUG: 17:03:00.411: Device reported verify completion 302s (process:2174): libfprint-device-DEBUG: 17:03:00.411: Device reported finger status change: FP_FINGER_STATUS_NONE 302s (process:2174): libfprint-device-DEBUG: 17:03:00.411: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 302s (process:2174): libfprint-device-DEBUG: 17:03:00.411: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 302s (process:2174): libfprint-device-DEBUG: 17:03:00.411: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.411: Activating image device 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.411: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.411: Image device activation completed 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.411: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.411: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 302s (process:2174): libfprint-device-DEBUG: 17:03:00.411: Device reported finger status change: FP_FINGER_STATUS_NEEDED 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.411: Deactivating image device 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.411: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.411: Image device deactivation completed 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.411: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 302s (process:2174): libfprint-device-DEBUG: 17:03:00.411: Device reported generic error (An unspecified error occurred!) during action; action was: FPI_DEVICE_ACTION_VERIFY 302s (process:2174): libfprint-device-DEBUG: 17:03:00.411: Device reported verify completion 302s (process:2174): libfprint-device-DEBUG: 17:03:00.411: Device reported finger status change: FP_FINGER_STATUS_NONE 302s (process:2174): libfprint-device-DEBUG: 17:03:00.412: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 302s (process:2174): libfprint-device-DEBUG: 17:03:00.412: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 302s (process:2174): libfprint-virtual_image-DEBUG: 17:03:00.412: 136397062: ../libfprint/drivers/virtual-image.c:244 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.512: Image device close completed 302s (process:2174): libfprint-device-DEBUG: 17:03:00.512: Device reported close completion 302s (process:2174): libfprint-device-DEBUG: 17:03:00.512: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 302s (process:2174): libfprint-device-DEBUG: 17:03:00.512: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 302s Print was processed, continuing 302s Print was processed, continuing 302s Print was processed, continuing 302s Print was processed, continuing 302s Print was processed, continuing 302s Enroll done 302s Print was processed, continuing 302s Print was processed, continuing 302s Print was processed, continuing 302s Print was processed, continuing 302s Print was processed, continuing 302s Enroll done 302s fp - device - error - quark: An unspecified error occurred! (0) 302s ok 302s test_features (__main__.VirtualImage.test_features) ... (process:2174): libfprint-virtual_image-DEBUG: 17:03:00.512: 136497478: ../libfprint/drivers/virtual-image.c:216 302s (process:2174): libfprint-virtual_device_connection-DEBUG: 17:03:00.512: 136497488: ../libfprint/drivers/virtual-device-listener.c:153 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.612: Image device open completed 302s (process:2174): libfprint-device-DEBUG: 17:03:00.612: Device reported open completion 302s (process:2174): libfprint-device-DEBUG: 17:03:00.612: Completing action FPI_DEVICE_ACTION_OPEN in idle! 302s (process:2174): libfprint-device-DEBUG: 17:03:00.612: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 302s (process:2174): libfprint-virtual_image-DEBUG: 17:03:00.613: 136598046: ../libfprint/drivers/virtual-image.c:244 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.713: Image device close completed 302s (process:2174): libfprint-device-DEBUG: 17:03:00.713: Device reported close completion 302s (process:2174): libfprint-device-DEBUG: 17:03:00.713: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 302s (process:2174): libfprint-device-DEBUG: 17:03:00.713: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 302s ok 302s test_identify (__main__.VirtualImage.test_identify) ... (process:2174): libfprint-virtual_image-DEBUG: 17:03:00.713: 136698439: ../libfprint/drivers/virtual-image.c:216 302s (process:2174): libfprint-virtual_device_connection-DEBUG: 17:03:00.713: 136698448: ../libfprint/drivers/virtual-device-listener.c:153 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.813: Image device open completed 302s (process:2174): libfprint-device-DEBUG: 17:03:00.813: Device reported open completion 302s (process:2174): libfprint-device-DEBUG: 17:03:00.813: Completing action FPI_DEVICE_ACTION_OPEN in idle! 302s (process:2174): libfprint-device-DEBUG: 17:03:00.813: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 302s (process:2174): libfprint-device-DEBUG: 17:03:00.814: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.814: Activating image device 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.814: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.814: Image device activation completed 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.814: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.814: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 302s (process:2174): libfprint-device-DEBUG: 17:03:00.814: Device reported finger status change: FP_FINGER_STATUS_NEEDED 302s (process:2174): libfprint-virtual_device_connection-DEBUG: 17:03:00.814: Got a new connection! 302s (process:2174): libfprint-virtual_image-DEBUG: 17:03:00.814: image data: 0x15cf2760 302s (process:2174): libfprint-device-DEBUG: 17:03:00.814: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.814: Image device reported finger status: on 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.814: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.814: Image device captured an image 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.814: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 302s (process:2174): libfprint-device-DEBUG: 17:03:00.814: Device reported finger status change: FP_FINGER_STATUS_PRESENT 302s (process:2174): libfprint-device-DEBUG: 17:03:00.814: Device reported finger status change: FP_FINGER_STATUS_NONE 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.814: Image device reported finger status: off 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.814: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 302s (process:2174): libfprint-image-DEBUG: 17:03:00.837: Minutiae scan completed in 0.022669 secs 302s (process:2174): libfprint-device-DEBUG: 17:03:00.837: Device reported enroll progress, reported 1 of 5 have been completed 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.837: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 302s (process:2174): libfprint-device-DEBUG: 17:03:00.837: Device reported finger status change: FP_FINGER_STATUS_NEEDED 302s (process:2174): libfprint-device-DEBUG: 17:03:00.837: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.837: Image device reported finger status: on 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.837: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 302s (process:2174): libfprint-virtual_image-DEBUG: 17:03:00.838: image data: 0x15cf2760 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.838: Image device captured an image 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.839: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 302s (process:2174): libfprint-device-DEBUG: 17:03:00.839: Device reported finger status change: FP_FINGER_STATUS_PRESENT 302s (process:2174): libfprint-image-DEBUG: 17:03:00.861: Minutiae scan completed in 0.022779 secs 302s (process:2174): libfprint-device-DEBUG: 17:03:00.861: Device reported enroll progress, reported 2 of 5 have been completed 302s (process:2174): libfprint-device-DEBUG: 17:03:00.861: Device reported finger status change: FP_FINGER_STATUS_NONE 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.861: Image device reported finger status: off 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.861: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.861: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 302s (process:2174): libfprint-device-DEBUG: 17:03:00.861: Device reported finger status change: FP_FINGER_STATUS_NEEDED 302s (process:2174): libfprint-virtual_image-DEBUG: 17:03:00.861: image data: 0x15cf2760 302s (process:2174): libfprint-device-DEBUG: 17:03:00.861: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.861: Image device reported finger status: on 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.861: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.861: Image device captured an image 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.863: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 302s (process:2174): libfprint-device-DEBUG: 17:03:00.863: Device reported finger status change: FP_FINGER_STATUS_PRESENT 302s (process:2174): libfprint-device-DEBUG: 17:03:00.863: Device reported finger status change: FP_FINGER_STATUS_NONE 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.863: Image device reported finger status: off 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.863: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 302s (process:2174): libfprint-image-DEBUG: 17:03:00.884: Minutiae scan completed in 0.022913 secs 302s (process:2174): libfprint-device-DEBUG: 17:03:00.885: Device reported enroll progress, reported 3 of 5 have been completed 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.885: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 302s (process:2174): libfprint-device-DEBUG: 17:03:00.885: Device reported finger status change: FP_FINGER_STATUS_NEEDED 302s (process:2174): libfprint-virtual_image-DEBUG: 17:03:00.885: image data: 0x15d00fc0 302s (process:2174): libfprint-device-DEBUG: 17:03:00.885: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.885: Image device reported finger status: on 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.885: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.885: Image device captured an image 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.885: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 302s (process:2174): libfprint-device-DEBUG: 17:03:00.885: Device reported finger status change: FP_FINGER_STATUS_PRESENT 302s (process:2174): libfprint-device-DEBUG: 17:03:00.885: Device reported finger status change: FP_FINGER_STATUS_NONE 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.885: Image device reported finger status: off 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.885: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 302s (process:2174): libfprint-image-DEBUG: 17:03:00.908: Minutiae scan completed in 0.022799 secs 302s (process:2174): libfprint-device-DEBUG: 17:03:00.908: Device reported enroll progress, reported 4 of 5 have been completed 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.908: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 302s (process:2174): libfprint-device-DEBUG: 17:03:00.908: Device reported finger status change: FP_FINGER_STATUS_NEEDED 302s (process:2174): libfprint-virtual_image-DEBUG: 17:03:00.908: image data: 0x15cf2760 302s (process:2174): libfprint-device-DEBUG: 17:03:00.908: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.908: Image device reported finger status: on 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.908: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.908: Image device captured an image 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.911: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 302s (process:2174): libfprint-device-DEBUG: 17:03:00.911: Device reported finger status change: FP_FINGER_STATUS_PRESENT 302s (process:2174): libfprint-device-DEBUG: 17:03:00.911: Device reported finger status change: FP_FINGER_STATUS_NONE 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.911: Image device reported finger status: off 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.911: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 302s (process:2174): libfprint-image-DEBUG: 17:03:00.931: Minutiae scan completed in 0.023092 secs 302s (process:2174): libfprint-device-DEBUG: 17:03:00.932: Device reported enroll progress, reported 5 of 5 have been completed 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.932: Deactivating image device 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.932: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.932: Image device deactivation completed 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.932: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 302s (process:2174): libfprint-device-DEBUG: 17:03:00.932: Device reported enroll completion 302s (process:2174): libfprint-device-DEBUG: 17:03:00.932: Print for finger FP_FINGER_LEFT_THUMB enrolled 302s (process:2174): libfprint-device-DEBUG: 17:03:00.932: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 302s (process:2174): libfprint-device-DEBUG: 17:03:00.932: Updated temperature model after 0.12 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 302s (process:2174): libfprint-device-DEBUG: 17:03:00.932: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.932: Activating image device 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.932: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.932: Image device activation completed 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.932: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.932: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 302s (process:2174): libfprint-device-DEBUG: 17:03:00.932: Device reported finger status change: FP_FINGER_STATUS_NEEDED 302s (process:2174): libfprint-virtual_image-DEBUG: 17:03:00.932: image data: 0x15d10000 302s (process:2174): libfprint-device-DEBUG: 17:03:00.932: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.932: Image device reported finger status: on 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.932: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.932: Image device captured an image 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.935: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 302s (process:2174): libfprint-device-DEBUG: 17:03:00.935: Device reported finger status change: FP_FINGER_STATUS_PRESENT 302s (process:2174): libfprint-device-DEBUG: 17:03:00.935: Device reported finger status change: FP_FINGER_STATUS_NONE 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.935: Image device reported finger status: off 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.935: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 302s (process:2174): libfprint-image-DEBUG: 17:03:00.953: Minutiae scan completed in 0.020718 secs 302s (process:2174): libfprint-device-DEBUG: 17:03:00.953: Device reported enroll progress, reported 1 of 5 have been completed 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.953: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 302s (process:2174): libfprint-device-DEBUG: 17:03:00.953: Device reported finger status change: FP_FINGER_STATUS_NEEDED 302s (process:2174): libfprint-device-DEBUG: 17:03:00.953: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.953: Image device reported finger status: on 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.953: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 302s (process:2174): libfprint-virtual_image-DEBUG: 17:03:00.953: image data: 0x15cf36c0 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.953: Image device captured an image 302s (process:2174): libfprint-image_device-DEBUG: 17:03:00.955: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 302s (process:2174): libfprint-device-DEBUG: 17:03:00.955: Device reported finger status change: FP_FINGER_STATUS_PRESENT 303s (process:2174): libfprint-image-DEBUG: 17:03:00.974: Minutiae scan completed in 0.020637 secs 303s (process:2174): libfprint-device-DEBUG: 17:03:00.974: Device reported enroll progress, reported 2 of 5 have been completed 303s (process:2174): libfprint-device-DEBUG: 17:03:00.974: Device reported finger status change: FP_FINGER_STATUS_NONE 303s (process:2174): libfprint-image_device-DEBUG: 17:03:00.974: Image device reported finger status: off 303s (process:2174): libfprint-image_device-DEBUG: 17:03:00.974: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 303s (process:2174): libfprint-image_device-DEBUG: 17:03:00.974: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 303s (process:2174): libfprint-device-DEBUG: 17:03:00.974: Device reported finger status change: FP_FINGER_STATUS_NEEDED 303s (process:2174): libfprint-virtual_image-DEBUG: 17:03:00.974: image data: 0x15d026d0 303s (process:2174): libfprint-device-DEBUG: 17:03:00.974: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 303s (process:2174): libfprint-image_device-DEBUG: 17:03:00.974: Image device reported finger status: on 303s (process:2174): libfprint-image_device-DEBUG: 17:03:00.974: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 303s (process:2174): libfprint-image_device-DEBUG: 17:03:00.974: Image device captured an image 303s (process:2174): libfprint-image_device-DEBUG: 17:03:00.974: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 303s (process:2174): libfprint-device-DEBUG: 17:03:00.974: Device reported finger status change: FP_FINGER_STATUS_PRESENT 303s (process:2174): libfprint-device-DEBUG: 17:03:00.974: Device reported finger status change: FP_FINGER_STATUS_NONE 303s (process:2174): libfprint-image_device-DEBUG: 17:03:00.974: Image device reported finger status: off 303s (process:2174): libfprint-image_device-DEBUG: 17:03:00.974: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 303s (process:2174): libfprint-image-DEBUG: 17:03:00.995: Minutiae scan completed in 0.020703 secs 303s (process:2174): libfprint-device-DEBUG: 17:03:00.995: Device reported enroll progress, reported 3 of 5 have been completed 303s (process:2174): libfprint-image_device-DEBUG: 17:03:00.996: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 303s (process:2174): libfprint-device-DEBUG: 17:03:00.996: Device reported finger status change: FP_FINGER_STATUS_NEEDED 303s (process:2174): libfprint-virtual_image-DEBUG: 17:03:00.996: image data: 0x15cf36c0 303s (process:2174): libfprint-device-DEBUG: 17:03:00.996: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 303s (process:2174): libfprint-image_device-DEBUG: 17:03:00.996: Image device reported finger status: on 303s (process:2174): libfprint-image_device-DEBUG: 17:03:00.996: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 303s (process:2174): libfprint-image_device-DEBUG: 17:03:00.996: Image device captured an image 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.003: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 303s (process:2174): libfprint-device-DEBUG: 17:03:01.003: Device reported finger status change: FP_FINGER_STATUS_PRESENT 303s (process:2174): libfprint-device-DEBUG: 17:03:01.003: Device reported finger status change: FP_FINGER_STATUS_NONE 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.003: Image device reported finger status: off 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.003: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 303s (process:2174): libfprint-image-DEBUG: 17:03:01.017: Minutiae scan completed in 0.020571 secs 303s (process:2174): libfprint-device-DEBUG: 17:03:01.017: Device reported enroll progress, reported 4 of 5 have been completed 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.017: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 303s (process:2174): libfprint-device-DEBUG: 17:03:01.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED 303s (process:2174): libfprint-virtual_image-DEBUG: 17:03:01.017: image data: 0x15d026d0 303s (process:2174): libfprint-device-DEBUG: 17:03:01.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.017: Image device reported finger status: on 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.017: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.017: Image device captured an image 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.017: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 303s (process:2174): libfprint-device-DEBUG: 17:03:01.017: Device reported finger status change: FP_FINGER_STATUS_PRESENT 303s (process:2174): libfprint-device-DEBUG: 17:03:01.017: Device reported finger status change: FP_FINGER_STATUS_NONE 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.017: Image device reported finger status: off 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.017: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 303s Executing: libfprint-2/virtual-image.test 303s (process:2174): libfprint-image-DEBUG: 17:03:01.038: Minutiae scan completed in 0.020999 secs 303s (process:2174): libfprint-device-DEBUG: 17:03:01.038: Device reported enroll progress, reported 5 of 5 have been completed 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.038: Deactivating image device 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.038: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.038: Image device deactivation completed 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.038: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 303s (process:2174): libfprint-device-DEBUG: 17:03:01.038: Device reported enroll completion 303s (process:2174): libfprint-device-DEBUG: 17:03:01.038: Print for finger FP_FINGER_LEFT_THUMB enrolled 303s (process:2174): libfprint-device-DEBUG: 17:03:01.038: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 303s (process:2174): libfprint-device-DEBUG: 17:03:01.038: Updated temperature model after 0.11 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 303s (process:2174): libfprint-device-DEBUG: 17:03:01.039: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.039: Activating image device 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.039: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.039: Image device activation completed 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.039: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.039: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 303s (process:2174): libfprint-device-DEBUG: 17:03:01.039: Device reported finger status change: FP_FINGER_STATUS_NEEDED 303s (process:2174): libfprint-virtual_image-DEBUG: 17:03:01.039: image data: 0x15d116e0 303s (process:2174): libfprint-device-DEBUG: 17:03:01.039: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.039: Image device reported finger status: on 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.039: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.039: Image device captured an image 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.043: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 303s (process:2174): libfprint-device-DEBUG: 17:03:01.043: Device reported finger status change: FP_FINGER_STATUS_PRESENT 303s (process:2174): libfprint-device-DEBUG: 17:03:01.043: Device reported finger status change: FP_FINGER_STATUS_NONE 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.043: Image device reported finger status: off 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.043: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.043: Deactivating image device 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.043: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.043: Image device deactivation completed 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.043: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 303s (process:2174): libfprint-image-DEBUG: 17:03:01.060: Minutiae scan completed in 0.020668 secs 303s (process:2174): libfprint-print-DEBUG: 17:03:01.066: score 10/40 303s (process:2174): libfprint-print-DEBUG: 17:03:01.071: score 10/40 303s (process:2174): libfprint-print-DEBUG: 17:03:01.077: score 10/40 303s (process:2174): libfprint-print-DEBUG: 17:03:01.082: score 10/40 303s (process:2174): libfprint-print-DEBUG: 17:03:01.088: score 10/40 303s (process:2174): libfprint-print-DEBUG: 17:03:01.282: score 855/40 303s (process:2174): libfprint-device-DEBUG: 17:03:01.282: Device reported identify result 303s (process:2174): libfprint-device-DEBUG: 17:03:01.282: Device reported identify completion 303s (process:2174): libfprint-device-DEBUG: 17:03:01.282: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 303s (process:2174): libfprint-device-DEBUG: 17:03:01.282: Updated temperature model after 0.24 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 303s (process:2174): libfprint-device-DEBUG: 17:03:01.282: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.282: Activating image device 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.282: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.282: Image device activation completed 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.282: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.283: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 303s (process:2174): libfprint-device-DEBUG: 17:03:01.283: Device reported finger status change: FP_FINGER_STATUS_NEEDED 303s (process:2174): libfprint-virtual_image-DEBUG: 17:03:01.283: image data: 0x15cf5910 303s (process:2174): libfprint-device-DEBUG: 17:03:01.283: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.283: Image device reported finger status: on 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.283: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.283: Image device captured an image 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.287: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 303s (process:2174): libfprint-device-DEBUG: 17:03:01.287: Device reported finger status change: FP_FINGER_STATUS_PRESENT 303s (process:2174): libfprint-device-DEBUG: 17:03:01.287: Device reported finger status change: FP_FINGER_STATUS_NONE 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.287: Image device reported finger status: off 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.287: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.287: Deactivating image device 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.287: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.287: Image device deactivation completed 303s (process:2174): libfprint-image_device-DEBUG: 17:03:01.287: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 303s (process:2174): libfprint-image-DEBUG: 17:03:01.306: Minutiae scan completed in 0.022961 secs 304s (process:2174): libfprint-print-DEBUG: 17:03:02.257: score 1093/40 304s (process:2174): libfprint-device-DEBUG: 17:03:02.258: Device reported identify result 304s (process:2174): libfprint-device-DEBUG: 17:03:02.258: Device reported identify completion 304s (process:2174): libfprint-device-DEBUG: 17:03:02.258: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 304s (process:2174): libfprint-device-DEBUG: 17:03:02.258: Updated temperature model after 0.98 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 304s (process:2174): libfprint-device-DEBUG: 17:03:02.258: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.258: Activating image device 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.258: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.258: Image device activation completed 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.258: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.258: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 304s (process:2174): libfprint-device-DEBUG: 17:03:02.258: Device reported finger status change: FP_FINGER_STATUS_NEEDED 304s (process:2174): libfprint-device-DEBUG: 17:03:02.258: Device reported identify result 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.258: Deactivating image device 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.258: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.258: Image device deactivation completed 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.258: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 304s (process:2174): libfprint-device-DEBUG: 17:03:02.259: Device reported identify completion 304s (process:2174): libfprint-device-DEBUG: 17:03:02.259: Device reported finger status change: FP_FINGER_STATUS_NONE 304s (process:2174): libfprint-device-DEBUG: 17:03:02.259: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 304s (process:2174): libfprint-device-DEBUG: 17:03:02.259: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 304s (process:2174): libfprint-device-DEBUG: 17:03:02.259: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.259: Activating image device 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.259: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.259: Image device activation completed 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.259: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.259: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 304s (process:2174): libfprint-device-DEBUG: 17:03:02.259: Device reported finger status change: FP_FINGER_STATUS_NEEDED 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.259: Deactivating image device 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.259: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.259: Image device deactivation completed 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.259: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 304s (process:2174): libfprint-device-DEBUG: 17:03:02.259: Device reported generic error (An unspecified error occurred!) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 304s (process:2174): libfprint-device-DEBUG: 17:03:02.259: Device reported identify completion 304s (process:2174): libfprint-device-DEBUG: 17:03:02.259: Device reported finger status change: FP_FINGER_STATUS_NONE 304s (process:2174): libfprint-device-DEBUG: 17:03:02.259: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 304s (process:2174): libfprint-device-DEBUG: 17:03:02.259: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 304s (process:2174): libfprint-virtual_image-DEBUG: 17:03:02.260: 138244976: ../libfprint/drivers/virtual-image.c:244 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.360: Image device close completed 304s (process:2174): libfprint-device-DEBUG: 17:03:02.360: Device reported close completion 304s (process:2174): libfprint-device-DEBUG: 17:03:02.360: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 304s (process:2174): libfprint-device-DEBUG: 17:03:02.360: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 304s Print was processed, continuing 304s Print was processed, continuing 304s Print was processed, continuing 304s Print was processed, continuing 304s Print was processed, continuing 304s Enroll done 304s Print was processed, continuing 304s Print was processed, continuing 304s Print was processed, continuing 304s Print was processed, continuing 304s Print was processed, continuing 304s Enroll done 304s Identify finished 304s Identify finished 304s Identify finished 304s fp - device - retry - quark: The swipe was too short, please try again. (1) 304s Identify finished 304s fp - device - error - quark: An unspecified error occurred! (0) 304s ok 304s test_verify_serialized (__main__.VirtualImage.test_verify_serialized) ... (process:2174): libfprint-virtual_image-DEBUG: 17:03:02.360: 138345750: ../libfprint/drivers/virtual-image.c:216 304s (process:2174): libfprint-virtual_device_connection-DEBUG: 17:03:02.360: 138345810: ../libfprint/drivers/virtual-device-listener.c:153 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.461: Image device open completed 304s (process:2174): libfprint-device-DEBUG: 17:03:02.461: Device reported open completion 304s (process:2174): libfprint-device-DEBUG: 17:03:02.461: Completing action FPI_DEVICE_ACTION_OPEN in idle! 304s (process:2174): libfprint-device-DEBUG: 17:03:02.461: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 304s (process:2174): libfprint-device-DEBUG: 17:03:02.461: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.461: Activating image device 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.461: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.461: Image device activation completed 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.462: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.462: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 304s (process:2174): libfprint-device-DEBUG: 17:03:02.462: Device reported finger status change: FP_FINGER_STATUS_NEEDED 304s (process:2174): libfprint-virtual_device_connection-DEBUG: 17:03:02.462: Got a new connection! 304s (process:2174): libfprint-virtual_image-DEBUG: 17:03:02.462: image data: 0x15cf5910 304s (process:2174): libfprint-device-DEBUG: 17:03:02.462: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.462: Image device reported finger status: on 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.462: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.462: Image device captured an image 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.467: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 304s (process:2174): libfprint-device-DEBUG: 17:03:02.467: Device reported finger status change: FP_FINGER_STATUS_PRESENT 304s (process:2174): libfprint-device-DEBUG: 17:03:02.467: Device reported finger status change: FP_FINGER_STATUS_NONE 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.467: Image device reported finger status: off 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.467: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 304s (process:2174): libfprint-image-DEBUG: 17:03:02.485: Minutiae scan completed in 0.022903 secs 304s (process:2174): libfprint-device-DEBUG: 17:03:02.485: Device reported enroll progress, reported 1 of 5 have been completed 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.485: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 304s (process:2174): libfprint-device-DEBUG: 17:03:02.485: Device reported finger status change: FP_FINGER_STATUS_NEEDED 304s (process:2174): libfprint-device-DEBUG: 17:03:02.485: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.485: Image device reported finger status: on 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.485: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 304s (process:2174): libfprint-virtual_image-DEBUG: 17:03:02.485: image data: 0x15d12a00 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.485: Image device captured an image 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.486: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 304s (process:2174): libfprint-device-DEBUG: 17:03:02.486: Device reported finger status change: FP_FINGER_STATUS_PRESENT 304s (process:2174): libfprint-image-DEBUG: 17:03:02.508: Minutiae scan completed in 0.022804 secs 304s (process:2174): libfprint-device-DEBUG: 17:03:02.509: Device reported enroll progress, reported 2 of 5 have been completed 304s (process:2174): libfprint-device-DEBUG: 17:03:02.509: Device reported finger status change: FP_FINGER_STATUS_NONE 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.509: Image device reported finger status: off 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.509: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.509: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 304s (process:2174): libfprint-device-DEBUG: 17:03:02.509: Device reported finger status change: FP_FINGER_STATUS_NEEDED 304s (process:2174): libfprint-virtual_image-DEBUG: 17:03:02.509: image data: 0x15d041a0 304s (process:2174): libfprint-device-DEBUG: 17:03:02.509: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.509: Image device reported finger status: on 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.509: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.509: Image device captured an image 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.511: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 304s (process:2174): libfprint-device-DEBUG: 17:03:02.511: Device reported finger status change: FP_FINGER_STATUS_PRESENT 304s (process:2174): libfprint-device-DEBUG: 17:03:02.511: Device reported finger status change: FP_FINGER_STATUS_NONE 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.511: Image device reported finger status: off 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.511: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 304s (process:2174): libfprint-image-DEBUG: 17:03:02.532: Minutiae scan completed in 0.022867 secs 304s (process:2174): libfprint-device-DEBUG: 17:03:02.532: Device reported enroll progress, reported 3 of 5 have been completed 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.532: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 304s (process:2174): libfprint-device-DEBUG: 17:03:02.532: Device reported finger status change: FP_FINGER_STATUS_NEEDED 304s (process:2174): libfprint-virtual_image-DEBUG: 17:03:02.532: image data: 0x15d21290 304s (process:2174): libfprint-device-DEBUG: 17:03:02.532: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.532: Image device reported finger status: on 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.532: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.532: Image device captured an image 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.535: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 304s (process:2174): libfprint-device-DEBUG: 17:03:02.535: Device reported finger status change: FP_FINGER_STATUS_PRESENT 304s (process:2174): libfprint-device-DEBUG: 17:03:02.535: Device reported finger status change: FP_FINGER_STATUS_NONE 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.535: Image device reported finger status: off 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.535: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 304s (process:2174): libfprint-image-DEBUG: 17:03:02.555: Minutiae scan completed in 0.022969 secs 304s (process:2174): libfprint-device-DEBUG: 17:03:02.555: Device reported enroll progress, reported 4 of 5 have been completed 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.555: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 304s (process:2174): libfprint-device-DEBUG: 17:03:02.555: Device reported finger status change: FP_FINGER_STATUS_NEEDED 304s (process:2174): libfprint-virtual_image-DEBUG: 17:03:02.556: image data: 0x15d04b10 304s (process:2174): libfprint-device-DEBUG: 17:03:02.556: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.556: Image device reported finger status: on 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.556: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.556: Image device captured an image 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.559: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 304s (process:2174): libfprint-device-DEBUG: 17:03:02.559: Device reported finger status change: FP_FINGER_STATUS_PRESENT 304s (process:2174): libfprint-device-DEBUG: 17:03:02.559: Device reported finger status change: FP_FINGER_STATUS_NONE 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.559: Image device reported finger status: off 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.559: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 304s (process:2174): libfprint-image-DEBUG: 17:03:02.579: Minutiae scan completed in 0.022799 secs 304s (process:2174): libfprint-device-DEBUG: 17:03:02.579: Device reported enroll progress, reported 5 of 5 have been completed 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.579: Deactivating image device 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.579: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.579: Image device deactivation completed 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.579: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 304s (process:2174): libfprint-device-DEBUG: 17:03:02.579: Device reported enroll completion 304s (process:2174): libfprint-device-DEBUG: 17:03:02.579: Print for finger FP_FINGER_LEFT_THUMB enrolled 304s (process:2174): libfprint-device-DEBUG: 17:03:02.579: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 304s (process:2174): libfprint-device-DEBUG: 17:03:02.579: Updated temperature model after 0.12 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 304s (process:2174): libfprint-device-DEBUG: 17:03:02.579: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.579: Activating image device 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.579: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.579: Image device activation completed 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.579: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.579: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 304s (process:2174): libfprint-device-DEBUG: 17:03:02.579: Device reported finger status change: FP_FINGER_STATUS_NEEDED 304s (process:2174): libfprint-virtual_image-DEBUG: 17:03:02.579: image data: 0x15d21c00 304s (process:2174): libfprint-device-DEBUG: 17:03:02.579: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.579: Image device reported finger status: on 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.579: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.579: Image device captured an image 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.579: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 304s (process:2174): libfprint-device-DEBUG: 17:03:02.579: Device reported finger status change: FP_FINGER_STATUS_PRESENT 304s (process:2174): libfprint-device-DEBUG: 17:03:02.579: Device reported finger status change: FP_FINGER_STATUS_NONE 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.579: Image device reported finger status: off 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.579: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.579: Deactivating image device 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.579: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.579: Image device deactivation completed 304s (process:2174): libfprint-image_device-DEBUG: 17:03:02.579: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 304s (process:2174): libfprint-image-DEBUG: 17:03:02.603: Minutiae scan completed in 0.023010 secs 305s (process:2174): libfprint-print-DEBUG: 17:03:03.551: score 1093/40 305s (process:2174): libfprint-device-DEBUG: 17:03:03.551: Device reported verify result 305s (process:2174): libfprint-device-DEBUG: 17:03:03.551: Device reported verify completion 305s (process:2174): libfprint-device-DEBUG: 17:03:03.552: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 305s (process:2174): libfprint-device-DEBUG: 17:03:03.552: Updated temperature model after 0.97 seconds, ratio 0.28 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 305s (process:2174): libfprint-device-DEBUG: 17:03:03.552: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 305s (process:2174): libfprint-image_device-DEBUG: 17:03:03.552: Activating image device 305s (process:2174): libfprint-image_device-DEBUG: 17:03:03.552: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 305s (process:2174): libfprint-image_device-DEBUG: 17:03:03.552: Image device activation completed 305s (process:2174): libfprint-image_device-DEBUG: 17:03:03.552: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 305s (process:2174): libfprint-image_device-DEBUG: 17:03:03.552: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 305s (process:2174): libfprint-device-DEBUG: 17:03:03.552: Device reported finger status change: FP_FINGER_STATUS_NEEDED 305s (process:2174): libfprint-virtual_image-DEBUG: 17:03:03.552: image data: 0x15d0cab0 305s (process:2174): libfprint-device-DEBUG: 17:03:03.552: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 305s (process:2174): libfprint-image_device-DEBUG: 17:03:03.552: Image device reported finger status: on 305s (process:2174): libfprint-image_device-DEBUG: 17:03:03.552: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 305s (process:2174): libfprint-image_device-DEBUG: 17:03:03.552: Image device captured an image 305s (process:2174): libfprint-image_device-DEBUG: 17:03:03.555: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 305s (process:2174): libfprint-device-DEBUG: 17:03:03.555: Device reported finger status change: FP_FINGER_STATUS_PRESENT 305s (process:2174): libfprint-device-DEBUG: 17:03:03.555: Device reported finger status change: FP_FINGER_STATUS_NONE 305s (process:2174): libfprint-image_device-DEBUG: 17:03:03.555: Image device reported finger status: off 305s (process:2174): libfprint-image_device-DEBUG: 17:03:03.555: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 305s (process:2174): libfprint-image_device-DEBUG: 17:03:03.555: Deactivating image device 305s (process:2174): libfprint-image_device-DEBUG: 17:03:03.555: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 305s (process:2174): libfprint-image_device-DEBUG: 17:03:03.555: Image device deactivation completed 305s (process:2174): libfprint-image_device-DEBUG: 17:03:03.555: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 305s (process:2174): libfprint-image-DEBUG: 17:03:03.573: Minutiae scan completed in 0.020476 secs 305s (process:2174): libfprint-print-DEBUG: 17:03:03.579: score 10/40 305s (process:2174): libfprint-print-DEBUG: 17:03:03.584: score 10/40 305s (process:2174): libfprint-print-DEBUG: 17:03:03.590: score 10/40 305s (process:2174): libfprint-print-DEBUG: 17:03:03.595: score 10/40 305s (process:2174): libfprint-print-DEBUG: 17:03:03.600: score 10/40 305s (process:2174): libfprint-device-DEBUG: 17:03:03.600: Device reported verify result 305s (process:2174): libfprint-device-DEBUG: 17:03:03.601: Device reported verify completion 305s (process:2174): libfprint-device-DEBUG: 17:03:03.601: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 305s (process:2174): libfprint-device-DEBUG: 17:03:03.601: Updated temperature model after 0.05 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 305s (process:2174): libfprint-virtual_image-DEBUG: 17:03:03.601: 139586178: ../libfprint/drivers/virtual-image.c:244 305s (process:2174): libfprint-image_device-DEBUG: 17:03:03.701: Image device close completed 305s (process:2174): libfprint-device-DEBUG: 17:03:03.701: Device reported close completion 305s (process:2174): libfprint-device-DEBUG: 17:03:03.701: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 305s (process:2174): libfprint-device-DEBUG: 17:03:03.701: Updated temperature model after 0.10 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 305s Print was processed, continuing 305s Print was processed, continuing 305s Print was processed, continuing 305s Print was processed, continuing 305s Print was processed, continuing 305s Enroll done 305s ok 305s 305s ---------------------------------------------------------------------- 305s Ran 5 tests in 6.075s 305s 305s OK 305s PASS: libfprint-2/virtual-image.test 305s Running test: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_current.test 305s TAP version 13 305s # random seed: R02S252f2df11945ed22093380ec15d401b7 305s 1..4 305s # Start of context tests 305s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 305s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 305s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xecd226932580, GType is 222100332244704 305s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 305s ok 1 /context/new 305s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 305s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 305s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 305s ok 2 /context/no-devices 305s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 305s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 305s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xecd226932580, GType is 222100332244704 305s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 305s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 305s # libfprint-context-DEBUG: created 305s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 305s # 305s # libfprint-device-DEBUG: Device reported probe completion 305s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 305s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 305s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 305s # 305s # libfprint-device-DEBUG: Device reported open completion 305s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 305s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 305s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 305s # 305s # libfprint-device-DEBUG: Device reported close completion 305s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 305s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 305s ok 3 /context/has-virtual-device 305s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 305s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 305s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xecd226932580, GType is 222100332244704 305s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 305s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 305s # libfprint-context-DEBUG: created 305s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 305s # 305s # libfprint-device-DEBUG: Device reported probe completion 305s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 305s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 305s ok 4 /context/enumerates-new-devices 305s # End of context tests 305s PASS: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_current.test 305s Running test: libfprint-2/driver-nb1010.test 305s ** (umockdev-run:2199): DEBUG: 17:03:03.762: umockdev.vala:123: Created udev test bed /tmp/umockdev.BJ6WJ2 305s ** (umockdev-run:2199): DEBUG: 17:03:03.762: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-7 305s ** (umockdev-run:2199): DEBUG: 17:03:03.766: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-7 (subsystem usb) 305s ** (umockdev-run:2199): DEBUG: 17:03:03.768: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.BJ6WJ2/dev/bus/usb/001/003 305s ** (umockdev-run:2199): DEBUG: 17:03:03.768: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1 305s ** (umockdev-run:2199): DEBUG: 17:03:03.772: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1 (subsystem usb) 305s ** (umockdev-run:2199): DEBUG: 17:03:03.773: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.BJ6WJ2/dev/bus/usb/001/001 305s ** (umockdev-run:2199): DEBUG: 17:03:03.774: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0 305s ** (umockdev-run:2199): DEBUG: 17:03:03.775: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0 (subsystem pci) 305s ** (umockdev-run:2199): DEBUG: 17:03:03.777: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:01.3 305s ** (umockdev-run:2199): DEBUG: 17:03:03.778: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:01.3 (subsystem pci) 305s (umockdev-run:2199): GLib-GIO-DEBUG: 17:03:03.780: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 305s (process:2203): libfprint-context-DEBUG: 17:03:03.826: Initializing FpContext (libfprint version 1.94.7+tod1) 305s (process:2203): libfprint-tod-DEBUG: 17:03:03.826: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 305s libusb: error [op_handle_events] cannot find handle for fd 9 305s libusb: error [op_handle_events] cannot find handle for fd 9 305s libusb: error [op_handle_events] cannot find handle for fd 9 305s libusb: error [op_handle_events] cannot find handle for fd 9 305s (process:2203): libfprint-context-DEBUG: 17:03:03.828: No driver found for USB device 1D6B:0002 305s (process:2203): libfprint-device-DEBUG: 17:03:03.828: Device reported probe completion 305s (process:2203): libfprint-device-DEBUG: 17:03:03.828: Completing action FPI_DEVICE_ACTION_PROBE in idle! 305s (process:2203): libfprint-device-DEBUG: 17:03:03.828: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 305s libusb: error [op_handle_events] cannot find handle for fd 9 305s libusb: error [op_handle_events] cannot find handle for fd 9 305s libusb: error [op_handle_events] cannot find handle for fd 9 305s libusb: error [op_handle_events] cannot find handle for fd 9 305s libusb: error [op_handle_events] cannot find handle for fd 9 305s libusb: error [op_handle_events] cannot find handle for fd 9 305s libusb: error [op_handle_events] cannot find handle for fd 9 305s libusb: error [op_handle_events] cannot find handle for fd 9 305s libusb: error [op_handle_events] cannot find handle for fd 9 305s libusb: error [op_handle_events] cannot find handle for fd 9 305s libusb: error [op_handle_events] cannot find handle for fd 9 305s (process:2203): libfprint-image_device-DEBUG: 17:03:03.830: Image device open completed 305s (process:2203): libfprint-device-DEBUG: 17:03:03.830: Device reported open completion 305s (process:2203): libfprint-nb1010-DEBUG: 17:03:03.830: nb1010 Initialized 305s (process:2203): libfprint-device-DEBUG: 17:03:03.830: Completing action FPI_DEVICE_ACTION_OPEN in idle! 305s (process:2203): libfprint-device-DEBUG: 17:03:03.830: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 305s (process:2203): libfprint-device-DEBUG: 17:03:03.831: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 305s (process:2203): libfprint-image_device-DEBUG: 17:03:03.831: Activating image device 305s (process:2203): libfprint-image_device-DEBUG: 17:03:03.831: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 305s (process:2203): libfprint-image_device-DEBUG: 17:03:03.831: Image device activation completed 305s (process:2203): libfprint-image_device-DEBUG: 17:03:03.831: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 305s (process:2203): libfprint-image_device-DEBUG: 17:03:03.831: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 305s (process:2203): libfprint-SSM-DEBUG: 17:03:03.831: [nb1010] M_LOOP_NUM_STATES entering state 0 305s (process:2203): libfprint-device-DEBUG: 17:03:03.831: Device reported finger status change: FP_FINGER_STATUS_NEEDED 305s (process:2203): libfprint-nb1010-DEBUG: 17:03:03.831: nb1010 Activated 305s (process:2203): libfprint-SSM-DEBUG: 17:03:03.881: [nb1010] M_LOOP_NUM_STATES entering state 1 305s (process:2203): libfprint-SSM-DEBUG: 17:03:03.881: [nb1010] M_LOOP_NUM_STATES entering state 2 305s (process:2203): libfprint-SSM-DEBUG: 17:03:03.882: [nb1010] M_LOOP_NUM_STATES entering state 3 305s (process:2203): libfprint-device-DEBUG: 17:03:03.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 305s (process:2203): libfprint-image_device-DEBUG: 17:03:03.882: Image device reported finger status: on 305s (process:2203): libfprint-image_device-DEBUG: 17:03:03.882: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 305s (process:2203): libfprint-SSM-DEBUG: 17:03:03.883: [nb1010] M_LOOP_NUM_STATES entering state 4 305s (process:2203): libfprint-SSM-DEBUG: 17:03:03.884: [nb1010] M_LOOP_NUM_STATES entering state 5 305s (process:2203): libfprint-SSM-DEBUG: 17:03:03.917: [nb1010] M_LOOP_NUM_STATES entering state 6 305s (process:2203): libfprint-image_device-DEBUG: 17:03:03.917: Image device captured an image 305s (process:2203): libfprint-image_device-DEBUG: 17:03:03.917: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 305s (process:2203): libfprint-device-DEBUG: 17:03:03.917: Device reported finger status change: FP_FINGER_STATUS_PRESENT 305s (process:2203): libfprint-SSM-DEBUG: 17:03:03.917: [nb1010] M_LOOP_NUM_STATES completed successfully 305s (process:2203): libfprint-nb1010-DEBUG: 17:03:03.917: nb1010 ssm complete cb 305s (process:2203): libfprint-device-DEBUG: 17:03:03.917: Device reported finger status change: FP_FINGER_STATUS_NONE 305s (process:2203): libfprint-image_device-DEBUG: 17:03:03.917: Image device reported finger status: off 305s (process:2203): libfprint-image_device-DEBUG: 17:03:03.917: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 305s (process:2203): libfprint-image_device-DEBUG: 17:03:03.917: Deactivating image device 305s (process:2203): libfprint-image_device-DEBUG: 17:03:03.917: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 305s (process:2203): libfprint-image_device-DEBUG: 17:03:03.917: Image device deactivation completed 305s (process:2203): libfprint-image_device-DEBUG: 17:03:03.917: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 305s (process:2203): libfprint-nb1010-DEBUG: 17:03:03.917: nb1010 Deactivated 305s (process:2203): libfprint-device-DEBUG: 17:03:03.931: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 305s (process:2203): libfprint-image-DEBUG: 17:03:03.941: Minutiae scan completed in 0.023134 secs 305s (process:2203): libfprint-device-DEBUG: 17:03:03.941: Device reported capture completion 305s (process:2203): libfprint-device-DEBUG: 17:03:03.941: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 305s (process:2203): libfprint-device-DEBUG: 17:03:03.941: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 305s (process:2203): libfprint-image_device-DEBUG: 17:03:03.941: Image device close completed 305s (process:2203): libfprint-device-DEBUG: 17:03:03.941: Device reported close completion 305s (process:2203): libfprint-nb1010-DEBUG: 17:03:03.941: nb1010 Deinitialized 305s (process:2203): libfprint-device-DEBUG: 17:03:03.941: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 305s (process:2203): libfprint-device-DEBUG: 17:03:03.941: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 306s ** (umockdev-run:2199): DEBUG: 17:03:04.006: umockdev.vala:150: Removing test bed /tmp/umockdev.BJ6WJ2 306s (umockdev-run:2199): GLib-DEBUG: 17:03:04.010: unsetenv() is not thread-safe and should not be used after threads are created 306s Comparing PNGs /tmp/libfprint-umockdev-test-aazcwifa/capture.png and /usr/share/installed-tests/libfprint-2/nb1010/capture.png 306s PASS: libfprint-2/driver-nb1010.test 306s Running test: libfprint-2/fpi-assembling.test 306s TAP version 13 306s # random seed: R02S2de7ae046e7465ae65a8e428204728c3 306s 1..1 306s # Start of assembling tests 306s # libfprint-assembling-DEBUG: calc delta completed in 0.098550 secs 306s # libfprint-assembling-DEBUG: calc delta completed in 0.098312 secs 306s # libfprint-assembling-DEBUG: errors: 0 rev: 130848 306s # libfprint-assembling-DEBUG: calc delta completed in 0.098275 secs 306s # libfprint-assembling-DEBUG: height is 310 306s ok 1 /assembling/frames 306s # End of assembling tests 306s PASS: libfprint-2/fpi-assembling.test 306s Running test: libfprint-2/driver-egis0570.test 306s ** (umockdev-run:2214): DEBUG: 17:03:04.372: umockdev.vala:123: Created udev test bed /tmp/umockdev.Q0UGK2 306s ** (umockdev-run:2214): DEBUG: 17:03:04.372: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 306s ** (umockdev-run:2214): DEBUG: 17:03:04.373: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 306s ** (umockdev-run:2214): DEBUG: 17:03:04.375: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.Q0UGK2/dev/bus/usb/001/005 306s ** (umockdev-run:2214): DEBUG: 17:03:04.376: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 306s ** (umockdev-run:2214): DEBUG: 17:03:04.376: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 306s ** (umockdev-run:2214): DEBUG: 17:03:04.378: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.Q0UGK2/dev/bus/usb/001/001 306s ** (umockdev-run:2214): DEBUG: 17:03:04.378: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 306s ** (umockdev-run:2214): DEBUG: 17:03:04.379: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 306s (process:2218): libfprint-context-DEBUG: 17:03:04.426: Initializing FpContext (libfprint version 1.94.7+tod1) 306s (process:2218): libfprint-tod-DEBUG: 17:03:04.426: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 306s (process:2218): libfprint-context-DEBUG: 17:03:04.428: No driver found for USB device 1D6B:0002 306s (process:2218): libfprint-device-DEBUG: 17:03:04.428: Device reported probe completion 306s (process:2218): libfprint-device-DEBUG: 17:03:04.428: Completing action FPI_DEVICE_ACTION_PROBE in idle! 306s (process:2218): libfprint-device-DEBUG: 17:03:04.428: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find ha(process:2218): libfprint-image_device-DEBUG: 17:03:04.431: Image device open completed 306s (process:2218): libfprint-device-DEBUG: 17:03:04.431: Device reported open completion 306s (process:2218): libfprint-device-DEBUG: 17:03:04.431: Completing action FPI_DEVICE_ACTION_OPEN in idle! 306s (process:2218): libfprint-device-DEBUG: 17:03:04.431: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 306s (process:2218): libfprint-device-DEBUG: 17:03:04.431: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.431: Activating image device 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.431: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.431: [egis0570] SM_STATES_NUM entering state 0 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.431: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.431: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.432: Image device activation completed 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.432: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.432: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 306s (process:2218): libfprint-device-DEBUG: 17:03:04.432: Device reported finger status change: FP_FINGER_STATUS_NEEDED 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.432: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.433: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.433: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.433: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.434: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.434: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.435: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.435: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.436: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.436: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.437: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.437: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.437: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.438: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.438: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.438: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.439: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.439: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.440: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.440: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.441: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.441: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.442: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.442: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.442: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.443: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.443: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.443: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.444: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.444: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.445: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.445: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.446: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.446: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.447: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.447: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.447: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.448: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.448: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.448: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.449: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.449: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.450: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.450: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.451: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.451: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.451: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.451: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.451: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.451: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.452: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.452: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.452: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.453: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.453: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.453: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.454: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.454: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.455: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.455: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.455: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.455: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.455: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.455: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.455: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.455: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.455: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.455: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.455: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.456: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.456: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.457: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.457: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.458: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.458: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.458: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.458: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.458: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.458: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.458: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.458: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.458: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.458: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.458: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.458: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.459: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.459: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.459: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.460: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.460: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.461: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.461: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.461: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.461: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.461: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.461: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.461: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.461: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.461: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.461: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.461: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.462: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.462: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.462: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.463: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.463: [egis0570] SM_STATES_NUM entering state 3 306s ndle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s libusb: error [op_handle_events] cannot find handle for fd 9 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.464: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.464: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.464: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.465: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.465: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.465: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.465: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.465: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.465: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.465: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.465: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.465: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.465: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.465: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.466: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.466: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.467: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.467: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.467: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.467: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.468: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.468: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.468: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.468: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.468: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.468: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.468: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.468: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.468: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.468: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.469: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.469: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.469: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.470: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.470: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.471: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.471: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.471: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.471: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.471: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.471: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.471: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.471: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.471: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.471: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.471: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.472: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.472: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.473: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.473: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.473: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.474: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.474: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.474: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.475: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.475: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.475: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.475: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.475: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.475: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.475: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.475: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.475: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.475: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.476: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.476: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.476: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.477: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.477: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.478: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.478: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.478: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.478: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.478: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.478: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.478: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.478: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.478: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.478: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.478: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.479: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.479: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.479: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.480: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.480: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.480: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.481: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.481: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.481: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.481: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.482: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.482: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.482: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.482: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.482: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.482: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.482: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.482: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.482: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.483: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.483: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.484: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.484: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.484: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.484: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.485: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.485: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.485: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.485: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.485: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.485: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.485: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.485: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.485: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.485: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.486: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.486: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.486: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.487: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.487: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.488: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.488: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.488: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.488: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.488: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.488: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.488: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.488: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.488: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.488: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.488: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.489: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.489: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.489: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.490: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.490: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.490: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.491: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.491: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.491: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.491: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.491: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.491: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.491: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.491: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.491: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.491: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.491: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.492: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.492: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.493: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.493: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.494: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.494: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.495: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.495: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.495: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.495: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.495: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.495: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.495: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.495: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.495: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.495: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.495: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.496: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.496: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.496: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.497: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.497: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.497: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.498: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.498: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.498: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.499: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.499: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.499: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.499: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.499: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.499: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.499: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.499: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.499: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.499: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.500: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.500: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.501: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.501: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.501: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.501: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.502: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.502: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.502: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.502: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.502: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.502: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.502: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.502: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.502: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.502: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.502: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.503: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.503: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.504: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.504: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.505: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.505: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.505: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.505: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.505: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.505: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.505: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.505: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.505: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.505: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.505: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.506: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.506: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.506: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.507: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.507: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.507: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.508: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.508: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.508: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.509: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.509: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.509: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.509: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.509: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.509: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.509: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.509: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.509: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.509: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.510: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.510: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.511: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.511: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.511: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.511: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.512: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.512: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.512: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.512: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.512: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.512: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.512: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.512: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.512: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.512: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.512: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.513: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.513: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.514: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.514: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.515: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.515: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.515: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.515: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.515: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.515: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.515: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.515: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.515: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.515: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.515: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.516: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.516: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.517: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.517: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.517: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.518: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.518: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.518: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.519: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.519: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.519: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.519: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.519: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.519: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.519: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.519: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.519: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.519: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.520: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.520: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.520: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.521: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.521: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.522: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.522: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.522: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.522: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.522: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.522: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.522: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.522: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.522: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.522: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.522: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.523: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.523: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.524: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.524: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.524: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.525: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.525: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.525: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.526: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.526: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.526: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.526: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.526: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.526: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.526: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.526: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.526: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.526: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.526: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.527: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.527: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.528: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.528: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.529: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.529: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.529: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.529: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.529: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.529: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.529: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.529: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.529: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.529: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.529: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.529: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.530: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.530: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.531: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-device-DEBUG: 17:03:04.531: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.531: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.531: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.532: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.532: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.533: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.533: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.533: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.533: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.533: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.533: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.533: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.533: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.533: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.533: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.533: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.534: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.534: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.534: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.535: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.535: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.535: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.536: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.536: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.536: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.536: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.536: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.536: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.536: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.536: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.536: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.536: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.536: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.537: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.537: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.538: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.538: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.538: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.538: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.539: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.539: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.539: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.539: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.539: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.539: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.539: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.539: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.539: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.539: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.540: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.540: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.540: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.541: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.541: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.542: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.542: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.542: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.542: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.542: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.542: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.542: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.542: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.542: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.542: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.542: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.543: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.543: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.543: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.544: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.544: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.544: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.545: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.545: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.545: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.546: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.546: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.546: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.546: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.546: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.546: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.546: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.546: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.546: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.546: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.547: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.547: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.548: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.548: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.548: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.548: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.549: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.549: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.549: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.549: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.549: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.549: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.549: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.549: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.549: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.549: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.550: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.550: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.550: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.551: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.551: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.552: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.552: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.552: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.552: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.552: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.552: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.552: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.552: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.552: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.552: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.552: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.553: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.553: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.553: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.554: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.554: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.554: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.555: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.555: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.556: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.556: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.556: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.556: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.556: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.556: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.556: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.556: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.556: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.556: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.556: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.557: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.557: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.558: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.558: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.558: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.558: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.559: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.559: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.559: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.559: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.559: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.559: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.559: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.559: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.559: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.559: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.560: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.560: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.560: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.561: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.561: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.562: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.562: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.562: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.562: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.562: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.562: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.562: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.562: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.562: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.562: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.562: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.563: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.563: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.564: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.564: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.564: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.565: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.565: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.565: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.566: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.566: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.566: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.566: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.566: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.566: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.566: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.566: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.566: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.566: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.566: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.567: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.567: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.568: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.568: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.569: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.569: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.569: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.569: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.569: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.569: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.569: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.569: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.569: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.569: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.569: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.570: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.570: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.571: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.571: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.571: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.572: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.572: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.572: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.573: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.573: Finger status (picture number, mean) : 1 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.573: Finger status (picture number, mean) : 2 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.573: Finger status (picture number, mean) : 3 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.573: Finger status (picture number, mean) : 4 , 0 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.573: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.573: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.573: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.573: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.573: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.573: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.574: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.574: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.575: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.575: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.575: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.575: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.576: Finger status (picture number, mean) : 0 , 0 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.576: Finger status (picture number, mean) : 1 , 1 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.576: Finger status (picture number, mean) : 2 , 2 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.576: Finger status (picture number, mean) : 3 , 3 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.576: Finger status (picture number, mean) : 4 , 6 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.576: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.576: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.576: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.576: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.576: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.576: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.577: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.577: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.578: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.578: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.579: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.579: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.579: Finger status (picture number, mean) : 0 , 11 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.579: Finger status (picture number, mean) : 1 , 16 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.579: Finger status (picture number, mean) : 2 , 23 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.579: Finger status (picture number, mean) : 3 , 28 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.579: Finger status (picture number, mean) : 4 , 32 306s (process:2218): libfprint-device-DEBUG: 17:03:04.579: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.579: Image device reported finger status: on 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.579: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 306s (process:2218): libfprint-device-DEBUG: 17:03:04.579: Device reported finger status change: FP_FINGER_STATUS_NEEDED 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.579: Image device reported finger status: off 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.579: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.579: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.579: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.580: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.580: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.581: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.581: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.581: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.582: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.582: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.582: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.583: Finger status (picture number, mean) : 0 , 38 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.583: Finger status (picture number, mean) : 1 , 43 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.583: Finger status (picture number, mean) : 2 , 48 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.583: Finger status (picture number, mean) : 3 , 54 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.583: Finger status (picture number, mean) : 4 , 58 306s (process:2218): libfprint-device-DEBUG: 17:03:04.583: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.583: Image device reported finger status: on 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.583: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.583: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.583: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.583: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.583: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.584: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.584: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.585: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.585: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.586: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.586: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.586: Finger status (picture number, mean) : 0 , 62 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.586: Finger status (picture number, mean) : 1 , 68 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.586: Finger status (picture number, mean) : 2 , 71 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.586: Finger status (picture number, mean) : 3 , 73 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.586: Finger status (picture number, mean) : 4 , 77 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.586: Image device reported finger status: on 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.586: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.586: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.586: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.587: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.587: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.588: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.588: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.588: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.589: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.589: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.589: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.590: Finger status (picture number, mean) : 0 , 79 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.590: Finger status (picture number, mean) : 1 , 79 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.590: Finger status (picture number, mean) : 2 , 82 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.590: Finger status (picture number, mean) : 3 , 84 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.590: Finger status (picture number, mean) : 4 , 85 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.590: Image device reported finger status: on 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.590: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.590: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.590: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.590: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.590: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.591: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.591: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.592: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.592: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.593: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.593: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.593: Finger status (picture number, mean) : 0 , 88 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.593: Finger status (picture number, mean) : 1 , 89 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.593: Finger status (picture number, mean) : 2 , 90 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.593: Finger status (picture number, mean) : 3 , 92 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.593: Finger status (picture number, mean) : 4 , 92 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.593: Image device reported finger status: on 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.593: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.593: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.593: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.593: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.594: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.594: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.594: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.595: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.595: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.596: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.596: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.596: Finger status (picture number, mean) : 0 , 93 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.596: Finger status (picture number, mean) : 1 , 94 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.596: Finger status (picture number, mean) : 2 , 95 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.596: Finger status (picture number, mean) : 3 , 96 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.596: Finger status (picture number, mean) : 4 , 97 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.596: Image device reported finger status: on 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.596: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.596: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.596: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.597: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.597: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.598: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.598: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.599: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.599: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.599: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.599: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.600: Finger status (picture number, mean) : 0 , 97 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.600: Finger status (picture number, mean) : 1 , 95 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.600: Finger status (picture number, mean) : 2 , 95 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.600: Finger status (picture number, mean) : 3 , 96 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.600: Finger status (picture number, mean) : 4 , 97 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.600: Image device reported finger status: on 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.600: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.600: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.600: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.600: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.600: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.601: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.601: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.602: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.602: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.603: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.603: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.603: Finger status (picture number, mean) : 0 , 96 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.603: Finger status (picture number, mean) : 1 , 97 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.603: Finger status (picture number, mean) : 2 , 98 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.603: Finger status (picture number, mean) : 3 , 98 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.603: Finger status (picture number, mean) : 4 , 98 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.603: Image device reported finger status: on 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.603: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.603: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.603: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.604: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.604: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.605: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.605: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.605: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.605: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.606: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.606: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.607: Finger status (picture number, mean) : 0 , 98 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.607: Finger status (picture number, mean) : 1 , 99 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.607: Finger status (picture number, mean) : 2 , 100 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.607: Finger status (picture number, mean) : 3 , 99 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.607: Finger status (picture number, mean) : 4 , 97 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.607: Image device reported finger status: on 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.607: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.607: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.607: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.607: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.607: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.608: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.608: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.609: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.609: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.610: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.610: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.610: Finger status (picture number, mean) : 0 , 98 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.610: Finger status (picture number, mean) : 1 , 98 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.610: Finger status (picture number, mean) : 2 , 98 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.610: Finger status (picture number, mean) : 3 , 95 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.610: Finger status (picture number, mean) : 4 , 91 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.610: Image device reported finger status: on 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.610: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.610: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.610: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.610: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.611: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.611: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.612: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.612: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.612: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.613: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.613: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.614: Finger status (picture number, mean) : 0 , 88 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.614: Finger status (picture number, mean) : 1 , 88 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.614: Finger status (picture number, mean) : 2 , 88 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.614: Finger status (picture number, mean) : 3 , 87 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.614: Finger status (picture number, mean) : 4 , 89 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.614: Image device reported finger status: on 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.614: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.614: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.614: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.614: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.614: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.615: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.615: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.616: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.616: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.617: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.617: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.617: Finger status (picture number, mean) : 0 , 88 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.617: Finger status (picture number, mean) : 1 , 89 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.617: Finger status (picture number, mean) : 2 , 90 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.617: Finger status (picture number, mean) : 3 , 91 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.617: Finger status (picture number, mean) : 4 , 89 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.617: Image device reported finger status: on 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.617: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.617: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.617: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.618: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.618: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.618: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.619: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.619: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.619: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.620: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.620: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.621: Finger status (picture number, mean) : 0 , 90 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.621: Finger status (picture number, mean) : 1 , 89 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.621: Finger status (picture number, mean) : 2 , 85 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.621: Finger status (picture number, mean) : 3 , 75 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.621: Finger status (picture number, mean) : 4 , 46 306s (process:2218): libfprint-image_device-DEBUG: 17:03:04.621: Image device reported finger status: on 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.621: [egis0570] SM_STATES_NUM entering state 5 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.621: [egis0570] SM_STATES_NUM entering state 1 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.621: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.621: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.621: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.622: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.622: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.623: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.623: [egis0570] SM_STATES_NUM entering state 2 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.623: [egis0570] SM_STATES_NUM entering state 3 306s (process:2218): libfprint-SSM-DEBUG: 17:03:04.623: [egis0570] SM_STATES_NUM entering state 4 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.624: Finger status (picture number, mean) : 0 , 17 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.624: Finger status (picture number, mean) : 1 , 14 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.624: Finger status (picture number, mean) : 2 , 15 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.624: Finger status (picture number, mean) : 3 , 15 306s (process:2218): libfprint-egis0570-DEBUG: 17:03:04.624: Finger status (picture number, mean) : 4 , 15 306s (process:2218): libfprint-assembling-DEBUG: 17:03:04.788: calc delta completed in 0.164297 secs 306s (process:2218): libfprint-assembling-DEBUG: 17:03:04.948: calc delta completed in 0.159773 secs 306s (process:2218): libfprint-assembling-DEBUG: 17:03:04.948: errors: 10243 rev: 29954 307s (process:2218): libfprint-assembling-DEBUG: 17:03:05.109: calc delta completed in 0.160894 secs 307s (process:2218): libfprint-assembling-DEBUG: 17:03:05.109: height is 292 307s (process:2218): libfprint-image_device-DEBUG: 17:03:05.116: Image device captured an image 307s (process:2218): libfprint-image_device-DEBUG: 17:03:05.119: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 307s (process:2218): libfprint-device-DEBUG: 17:03:05.119: Device reported finger status change: FP_FINGER_STATUS_PRESENT 307s (process:2218): libfprint-device-DEBUG: 17:03:05.119: Device reported finger status change: FP_FINGER_STATUS_NONE 307s (process:2218): libfprint-image_device-DEBUG: 17:03:05.119: Image device reported finger status: off 307s (process:2218): libfprint-image_device-DEBUG: 17:03:05.119: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 307s (process:2218): libfprint-image_device-DEBUG: 17:03:05.119: Deactivating image device 307s (process:2218): libfprint-image_device-DEBUG: 17:03:05.119: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 307s (process:2218): libfprint-SSM-DEBUG: 17:03:05.119: [egis0570] SM_STATES_NUM entering state 5 307s (process:2218): libfprint-SSM-DEBUG: 17:03:05.119: [egis0570] SM_STATES_NUM entering state 1 307s (process:2218): libfprint-egis0570-DEBUG: 17:03:05.119: deactivating, marking completed 307s (process:2218): libfprint-SSM-DEBUG: 17:03:05.119: [egis0570] SM_STATES_NUM completed successfully 307s (process:2218): libfprint-image_device-DEBUG: 17:03:05.119: Image device deactivation completed 307s (process:2218): libfprint-image_device-DEBUG: 17:03:05.119: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 307s (process:2218): libfprint-image-DEBUG: 17:03:05.208: Minutiae scan completed in 0.090853 secs 307s (process:2218): libfprint-device-DEBUG: 17:03:05.208: Device reported capture completion 307s (process:2218): libfprint-device-DEBUG: 17:03:05.208: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 307s (process:2218): libfprint-device-DEBUG: 17:03:05.208: Updated temperature model after 0.68 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 307s (process:2218): libfprint-image_device-DEBUG: 17:03:05.208: Image device close completed 307s (process:2218): libfprint-device-DEBUG: 17:03:05.208: Device reported close completion 307s (process:2218): libfprint-device-DEBUG: 17:03:05.209: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 307s (process:2218): libfprint-device-DEBUG: 17:03:05.209: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 307s ** (umockdev-run:2214): DEBUG: 17:03:05.429: umockdev.vala:150: Removing test bed /tmp/umockdev.Q0UGK2 307s (umockdev-run:2214): GLib-DEBUG: 17:03:05.432: unsetenv() is not thread-safe and should not be used after threads are created 307s Comparing PNGs /tmp/libfprint-umockdev-test-e59owqou/capture.png and /usr/share/installed-tests/libfprint-2/egis0570/capture.png 307s PASS: libfprint-2/driver-egis0570.test 307s Running test: libfprint-2/fp-context.test 307s TAP version 13 307s # random seed: R02Sa4ef94e00db568075a18e71d1770765f 307s 1..9 307s # Start of context tests 307s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 307s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 307s ok 1 /context/new 307s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 307s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 307s ok 2 /context/no-devices 307s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 307s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 307s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 307s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-YBZDK2/virtual_image.socket 307s # libfprint-context-DEBUG: created 307s # libfprint-device-DEBUG: Device reported probe completion 307s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 307s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 307s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 307s ok 3 /context/has-virtual-device 307s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 307s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 307s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 307s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-ZH0DK2/virtual_image.socket 307s # libfprint-context-DEBUG: created 307s # libfprint-device-DEBUG: Device reported probe completion 307s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 307s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 307s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 307s ok 4 /context/enumerates-new-devices 307s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 307s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 307s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 307s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-2Z0DK2/virtual_image.socket 307s # libfprint-context-DEBUG: created 307s # libfprint-device-DEBUG: Device reported probe completion 307s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 307s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 307s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 307s ok 5 /context/remove-device-closed 307s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 307s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 307s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 307s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-I02DK2/virtual_image.socket 307s # libfprint-context-DEBUG: created 307s # libfprint-device-DEBUG: Device reported probe completion 307s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 307s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 307s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2225): libfprint-virtual_image-DEBUG: 17:03:05.503: 141488300: ../libfprint/drivers/virtual-image.c:216 307s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2225): libfprint-virtual_device_connection-DEBUG: 17:03:05.503: 141488398: ../libfprint/drivers/virtual-device-listener.c:153 307s # libfprint-image_device-DEBUG: Image device open completed 307s # libfprint-device-DEBUG: Device reported open completion 307s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 307s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 307s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2225): libfprint-virtual_image-DEBUG: 17:03:05.604: 141588971: ../libfprint/drivers/virtual-image.c:244 307s # libfprint-image_device-DEBUG: Image device close completed 307s # libfprint-device-DEBUG: Device reported close completion 307s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 307s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 307s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 307s ok 6 /context/remove-device-closing 307s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 307s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 307s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 307s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-5T1XJ2/virtual_image.socket 307s # libfprint-context-DEBUG: created 307s # libfprint-device-DEBUG: Device reported probe completion 307s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 307s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 307s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2225): libfprint-virtual_image-DEBUG: 17:03:05.705: 141690343: ../libfprint/drivers/virtual-image.c:216 307s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2225): libfprint-virtual_device_connection-DEBUG: 17:03:05.705: 141690359: ../libfprint/drivers/virtual-device-listener.c:153 307s # libfprint-image_device-DEBUG: Image device open completed 307s # libfprint-device-DEBUG: Device reported open completion 307s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 307s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 307s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2225): libfprint-virtual_image-DEBUG: 17:03:05.805: 141790900: ../libfprint/drivers/virtual-image.c:244 307s # libfprint-image_device-DEBUG: Image device close completed 307s # libfprint-device-DEBUG: Device reported close completion 307s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 307s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 307s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 307s ok 7 /context/remove-device-open 307s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 307s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 307s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 307s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-T744J2/virtual_image.socket 307s # libfprint-context-DEBUG: created 307s # libfprint-device-DEBUG: Device reported probe completion 307s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 307s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 307s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2225): libfprint-virtual_image-DEBUG: 17:03:05.907: 141892370: ../libfprint/drivers/virtual-image.c:216 307s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2225): libfprint-virtual_device_connection-DEBUG: 17:03:05.907: 141892384: ../libfprint/drivers/virtual-device-listener.c:153 308s # libfprint-image_device-DEBUG: Image device open completed 308s # libfprint-device-DEBUG: Device reported open completion 308s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 308s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 308s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2225): libfprint-virtual_image-DEBUG: 17:03:06.007: 141992677: ../libfprint/drivers/virtual-image.c:244 308s Executing: libfprint-2/fp-context.test 308s # libfprint-image_device-DEBUG: Image device close completed 308s # libfprint-device-DEBUG: Device reported close completion 308s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 308s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 308s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 308s ok 8 /context/remove-device-opening 308s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 308s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 308s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 308s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-8S7AK2/virtual_image.socket 308s # libfprint-context-DEBUG: created 308s # libfprint-device-DEBUG: Device reported probe completion 308s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 308s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 308s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2225): libfprint-virtual_image-DEBUG: 17:03:06.109: 142094073: ../libfprint/drivers/virtual-image.c:216 308s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2225): libfprint-virtual_device_connection-DEBUG: 17:03:06.109: 142094088: ../libfprint/drivers/virtual-device-listener.c:153 308s # libfprint-image_device-DEBUG: Image device open completed 308s # libfprint-device-DEBUG: Device reported open completion 308s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 308s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 308s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 308s # libfprint-image_device-DEBUG: Activating image device 308s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 308s # libfprint-image_device-DEBUG: Image device activation completed 308s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 308s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 308s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s # libfprint-image_device-DEBUG: Deactivating image device 308s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 308s # libfprint-image_device-DEBUG: Image device deactivation completed 308s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 308s # libfprint-device-DEBUG: Device reported generic error (The driver encountered a protocol error with the device.) during action; action was: FPI_DEVICE_ACTION_ENROLL 308s # libfprint-device-DEBUG: Device reported enroll completion 308s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 308s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 308s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 308s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2225): libfprint-virtual_image-DEBUG: 17:03:06.209: 142194551: ../libfprint/drivers/virtual-image.c:244 308s # libfprint-image_device-DEBUG: Image device close completed 308s # libfprint-device-DEBUG: Device reported close completion 308s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 308s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 308s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 308s ok 9 /context/remove-device-active 308s # End of context tests 308s PASS: libfprint-2/fp-context.test 308s Running test: libfprint-2/driver-synaptics.test 308s ** (umockdev-run:2249): DEBUG: 17:03:06.346: umockdev.vala:123: Created udev test bed /tmp/umockdev.7CLFK2 308s ** (umockdev-run:2249): DEBUG: 17:03:06.346: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 308s ** (umockdev-run:2249): DEBUG: 17:03:06.347: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 308s ** (umockdev-run:2249): DEBUG: 17:03:06.349: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.7CLFK2/dev/bus/usb/001/004 308s ** (umockdev-run:2249): DEBUG: 17:03:06.349: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 308s ** (umockdev-run:2249): DEBUG: 17:03:06.350: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 308s ** (umockdev-run:2249): DEBUG: 17:03:06.352: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.7CLFK2/dev/bus/usb/001/001 308s ** (umockdev-run:2249): DEBUG: 17:03:06.352: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 308s ** (umockdev-run:2249): DEBUG: 17:03:06.352: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 308s (process:2253): libfprint-context-DEBUG: 17:03:06.398: Initializing FpContext (libfprint version 1.94.7+tod1) 308s (process:2253): libfprint-tod-DEBUG: 17:03:06.399: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 308s (process:2253): libfprint-context-DEBUG: 17:03:06.400: No driver found for USB device 1D6B:0002 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.401: 142386040: ../libfprint/drivers/synaptics/synaptics.c:1240 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find ha(process:2253): libfprint-synaptics-DEBUG: 17:03:06.404: Build Time: 1596608839 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.404: Build Num: 3273255 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.404: Version: 10.1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.404: Target: 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.404: Product: 65 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.404: sequence number is 1 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.404: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.405: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.405: Device reported probe completion 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.405: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 308s (process:2253): libfprint-device-DEBUG: 17:03:06.405: Completing action FPI_DEVICE_ACTION_PROBE in idle! 308s (process:2253): libfprint-device-DEBUG: 17:03:06.405: Not updating temperature model, device can run continuously! 308s ndle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.407: 142392047: ../libfprint/drivers/synaptics/synaptics.c:1400 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.407: sequence number is 2 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.407: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.407: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.408: Device reported open completion 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.408: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 308s (process:2253): libfprint-device-DEBUG: 17:03:06.408: Completing action FPI_DEVICE_ACTION_OPEN in idle! 308s (process:2253): libfprint-device-DEBUG: 17:03:06.408: Not updating temperature model, device can run continuously! 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.408: clear all prints in database 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.408: sequence number is 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.408: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.408: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.409: Deleting All Enrolled Users is 0% complete 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.409: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.409: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.409: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.409: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.410: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.410: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.410: Deleting All Enrolled Users is 100% complete 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.410: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.410: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.410: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.411: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.411: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.411: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.411: Successfully deleted all enrolled user 308s (process:2253): libfprint-device-DEBUG: 17:03:06.411: Device reported deletion completion 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.411: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 308s (process:2253): libfprint-device-DEBUG: 17:03:06.411: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 308s (process:2253): libfprint-device-DEBUG: 17:03:06.411: Not updating temperature model, device can run continuously! 308s (process:2253): libfprint-device-DEBUG: 17:03:06.412: Not updating temperature model, device can run continuously! 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.412: 142397406: ../libfprint/drivers/synaptics/synaptics.c:1011 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.412: user_id: FP1-00000000-0-00000000-nobody, finger: 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.412: sequence number is 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.412: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.412: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.413: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.413: Place Finger on the Sensor! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.413: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.413: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.413: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.414: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.414: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.414: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.414: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.414: Finger is now on the sensor 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.414: Received message with 0 sequence number 0x91, ignoring! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.414: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.415: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.415: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.415: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.415: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.415: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.416: Fingerprint image capture complete! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.416: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.416: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.416: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.416: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.416: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.416: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.417: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.417: Finger is now off the sensor 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.417: Received message with 0 sequence number 0x91, ignoring! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.417: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.417: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.417: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.418: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.418: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.418: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.418: Enrollment is 12 % 308s (process:2253): libfprint-device-DEBUG: 17:03:06.418: Device reported enroll progress, reported 1 of 8 have been completed 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.418: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.419: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.419: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.419: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.419: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.419: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.420: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.420: Finger is now on the sensor 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.420: Received message with 0 sequence number 0x91, ignoring! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.420: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.420: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.420: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.420: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.420: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.420: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.421: Fingerprint image capture complete! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.421: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.421: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.421: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.422: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.422: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.422: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.422: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.422: Finger is now off the sensor 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.422: Received message with 0 sequence number 0x91, ignoring! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.422: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.423: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.423: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.423: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.423: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.423: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.423: Enrollment is 25 % 308s (process:2253): libfprint-device-DEBUG: 17:03:06.423: Device reported enroll progress, reported 2 of 8 have been completed 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.423: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.424: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.424: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.424: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.424: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.424: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.425: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.425: Finger is now on the sensor 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.425: Received message with 0 sequence number 0x91, ignoring! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.425: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.425: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.425: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.426: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.426: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.426: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.426: Fingerprint image capture complete! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.426: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.426: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.426: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.427: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.427: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.427: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.427: Enrollment is 37 % 308s (process:2253): libfprint-device-DEBUG: 17:03:06.427: Device reported enroll progress, reported 3 of 8 have been completed 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.427: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.428: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.428: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.428: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.428: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.428: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.429: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.429: Finger is now off the sensor 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.429: Received message with 0 sequence number 0x91, ignoring! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.429: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.429: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.429: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.430: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.430: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.430: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.430: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.430: Finger is now on the sensor 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.430: Received message with 0 sequence number 0x91, ignoring! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.430: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.430: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.430: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.431: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.431: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.431: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.431: Fingerprint image capture complete! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.431: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.432: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.432: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.432: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.432: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.432: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.433: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.433: Finger is now off the sensor 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.433: Received message with 0 sequence number 0x91, ignoring! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.433: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.433: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.433: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.433: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.433: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.433: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.434: Enrollment is 50 % 308s (process:2253): libfprint-device-DEBUG: 17:03:06.434: Device reported enroll progress, reported 4 of 8 have been completed 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.434: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.434: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.434: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.435: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.435: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.435: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.435: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.435: Finger is now on the sensor 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.435: Received message with 0 sequence number 0x91, ignoring! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.435: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.435: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.435: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.436: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.436: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.436: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.436: Fingerprint image capture complete! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.436: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.437: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.437: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.437: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.437: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.437: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.438: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.438: Finger is now off the sensor 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.438: Received message with 0 sequence number 0x91, ignoring! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.438: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.438: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.438: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.438: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.438: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.438: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.439: Enrollment is 62 % 308s (process:2253): libfprint-device-DEBUG: 17:03:06.439: Device reported enroll progress, reported 5 of 8 have been completed 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.439: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.439: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.439: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.440: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.440: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.440: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.440: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.440: Finger is now on the sensor 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.440: Received message with 0 sequence number 0x91, ignoring! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.440: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.441: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.441: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.441: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.441: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.441: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.442: Fingerprint image capture complete! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.442: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.442: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.442: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.442: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.442: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.442: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.443: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.443: Finger is now off the sensor 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.443: Received message with 0 sequence number 0x91, ignoring! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.443: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.443: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.443: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.444: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.444: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.444: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.444: Enrollment is 62 % 308s (process:2253): libfprint-device-DEBUG: 17:03:06.444: Device reported enroll progress, reported 5 of 8 have been completed 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.444: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.445: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.445: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.445: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.445: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.445: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.445: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.445: Finger is now on the sensor 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.445: Received message with 0 sequence number 0x91, ignoring! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.445: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.446: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.446: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.446: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.446: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.446: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.447: Fingerprint image capture complete! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.447: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.447: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.447: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.448: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.448: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.448: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.448: Enrollment is 75 % 308s (process:2253): libfprint-device-DEBUG: 17:03:06.448: Device reported enroll progress, reported 6 of 8 have been completed 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.448: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.449: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.449: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.449: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.449: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.449: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.449: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.449: Finger is now off the sensor 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.449: Received message with 0 sequence number 0x91, ignoring! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.449: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.450: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.450: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.450: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.450: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.450: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.451: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.451: Finger is now on the sensor 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.451: Received message with 0 sequence number 0x91, ignoring! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.451: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.451: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.451: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.452: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.452: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.452: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.452: Fingerprint image capture complete! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.452: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.452: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.452: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.453: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.453: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.453: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.453: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.453: Finger is now off the sensor 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.453: Received message with 0 sequence number 0x91, ignoring! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.453: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.454: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.454: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.454: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.454: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.454: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.455: Enrollment is 87 % 308s (process:2253): libfprint-device-DEBUG: 17:03:06.455: Device reported enroll progress, reported 7 of 8 have been completed 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.455: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.455: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.455: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.456: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.456: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.456: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.456: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.456: Finger is now on the sensor 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.456: Received message with 0 sequence number 0x91, ignoring! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.456: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.456: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.456: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.457: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.457: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.457: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.457: Fingerprint image capture complete! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.457: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.458: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.458: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s libusb: warning [libusb_exit] device 1.1 still referenced 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.458: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.458: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.458: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.459: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.459: Finger is now off the sensor 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.459: Received message with 0 sequence number 0x91, ignoring! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.459: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.459: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.459: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.460: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.460: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.460: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.460: Enrollment is 100 % 308s (process:2253): libfprint-device-DEBUG: 17:03:06.460: Device reported enroll progress, reported 8 of 8 have been completed 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.460: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.461: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.461: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.461: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.461: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.461: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.461: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.461: Finger is now on the sensor 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.461: Received message with 0 sequence number 0x91, ignoring! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.461: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.462: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.462: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.462: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.462: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.462: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.463: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.463: Finger is now off the sensor 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.463: Received message with 0 sequence number 0x91, ignoring! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.463: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.463: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.463: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.464: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.464: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.464: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.464: Enrollment was successful! 308s (process:2253): libfprint-device-DEBUG: 17:03:06.464: Device reported enroll completion 308s (process:2253): libfprint-device-DEBUG: 17:03:06.464: Device reported finger status change: FP_FINGER_STATUS_NONE 308s (process:2253): libfprint-device-DEBUG: 17:03:06.464: Print for finger FP_FINGER_UNKNOWN enrolled 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.464: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 308s (process:2253): libfprint-device-DEBUG: 17:03:06.464: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 308s (process:2253): libfprint-device-DEBUG: 17:03:06.464: Not updating temperature model, device can run continuously! 308s (process:2253): libfprint-device-DEBUG: 17:03:06.464: Not updating temperature model, device can run continuously! 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.464: data is 0x2709cbd0 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.464: 142449750: ../libfprint/drivers/synaptics/synaptics.c:643 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.464: sequence number is 5 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.464: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.465: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.465: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.465: Place Finger on the Sensor! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.465: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.466: got suspend request 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.466: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.466: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 5 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.467: got resume request 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.467: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 6 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.467: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.468: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.468: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.468: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.468: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.468: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.468: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.468: Finger is now on the sensor 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.468: Received message with 0 sequence number 0x91, ignoring! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.468: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.469: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.469: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.469: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.469: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.469: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.470: Fingerprint image capture complete! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.470: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.470: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.470: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.471: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.471: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.471: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-device-DEBUG: 17:03:06.471: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.471: Finger is now off the sensor 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.471: Received message with 0 sequence number 0x91, ignoring! 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.471: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.472: interrupt transfer done 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.472: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.472: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.472: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.472: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.473: Verify was successful! for user: FP1-00000000-0-00000000-nobody finger: 1 score: 61.800000 308s (process:2253): libfprint-device-DEBUG: 17:03:06.473: Device reported verify result 308s (process:2253): libfprint-device-DEBUG: 17:03:06.473: Device reported verify completion 308s (process:2253): libfprint-device-DEBUG: 17:03:06.473: Device reported finger status change: FP_FINGER_STATUS_NONE 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.473: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 308s (process:2253): libfprint-device-DEBUG: 17:03:06.473: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 308s (process:2253): libfprint-device-DEBUG: 17:03:06.473: Not updating temperature model, device can run continuously! 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.473: data is 0x2709cbd0 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.473: 142458123: ../libfprint/drivers/synaptics/synaptics.c:1120 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.473: sequence number is 6 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.473: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.473: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.474: Successfully deleted enrolled user 308s (process:2253): libfprint-device-DEBUG: 17:03:06.474: Device reported deletion completion 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.474: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 308s (process:2253): libfprint-device-DEBUG: 17:03:06.474: Completing action FPI_DEVICE_ACTION_DELETE in idle! 308s (process:2253): libfprint-device-DEBUG: 17:03:06.474: Not updating temperature model, device can run continuously! 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.474: 142459055: ../libfprint/drivers/synaptics/synaptics.c:1421 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.474: sequence number is 7 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.474: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.474: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 308s (process:2253): libfprint-synaptics-DEBUG: 17:03:06.475: Fingerprint sensor ready to be powered down 308s (process:2253): libfprint-device-DEBUG: 17:03:06.475: Device reported close completion 308s (process:2253): libfprint-SSM-DEBUG: 17:03:06.475: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 308s (process:2253): libfprint-device-DEBUG: 17:03:06.475: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 308s (process:2253): libfprint-device-DEBUG: 17:03:06.475: Not updating temperature model, device can run continuously! 308s enrolling 308s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xe3f9ff395a00 (FpiDeviceSynaptics at 0x2709faa0)>, 1, None, None, None) 308s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xe3f9ff395a00 (FpiDeviceSynaptics at 0x2709faa0)>, 2, None, None, None) 308s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xe3f9ff395a00 (FpiDeviceSynaptics at 0x2709faa0)>, 3, None, None, None) 308s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xe3f9ff395a00 (FpiDeviceSynaptics at 0x2709faa0)>, 4, None, None, None) 308s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xe3f9ff395a00 (FpiDeviceSynaptics at 0x2709faa0)>, 5, None, None, None) 308s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xe3f9ff395a00 (FpiDeviceSynaptics at 0x2709faa0)>, 5, None, None, GLib.Error('Please try again.', 'fp - device - retry - quark', 0)) 308s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xe3f9ff395a00 (FpiDeviceSynaptics at 0x2709faa0)>, 6, None, None, None) 308s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xe3f9ff395a00 (FpiDeviceSynaptics at 0x2709faa0)>, 7, None, None, None) 308s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xe3f9ff395a00 (FpiDeviceSynaptics at 0x2709faa0)>, 8, None, None, None) 308s enroll done 308s verifying 308s verify done 308s deleting 308s delete done 308s ** (umockdev-run:2249): DEBUG: 17:03:06.486: umockdev.vala:150: Removing test bed /tmp/umockdev.7CLFK2 308s (umockdev-run:2249): GLib-DEBUG: 17:03:06.489: unsetenv() is not thread-safe and should not be used after threads are created 308s PASS: libfprint-2/driver-synaptics.test 308s Running test: libfprint-2/driver-goodixmoc.test 308s ** (umockdev-run:2261): DEBUG: 17:03:06.531: umockdev.vala:123: Created udev test bed /tmp/umockdev.1ON0J2 308s ** (umockdev-run:2261): DEBUG: 17:03:06.532: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-9 308s ** (umockdev-run:2261): DEBUG: 17:03:06.533: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-9 (subsystem usb) 308s ** (umockdev-run:2261): DEBUG: 17:03:06.535: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.1ON0J2/dev/bus/usb/003/004 308s ** (umockdev-run:2261): DEBUG: 17:03:06.535: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3 308s ** (umockdev-run:2261): DEBUG: 17:03:06.536: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb) 308s ** (umockdev-run:2261): DEBUG: 17:03:06.538: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.1ON0J2/dev/bus/usb/003/001 308s ** (umockdev-run:2261): DEBUG: 17:03:06.538: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 308s ** (umockdev-run:2261): DEBUG: 17:03:06.538: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 308s (process:2265): libfprint-context-DEBUG: 17:03:06.585: Initializing FpContext (libfprint version 1.94.7+tod1) 308s (process:2265): libfprint-tod-DEBUG: 17:03:06.585: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 308s (process:2265): libfprint-context-DEBUG: 17:03:06.587: No driver found for USB device 1D6B:0002 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s (process:2265): libfprint-device-DEBUG: 17:03:06.590: Device reported probe completion 308s (process:2265): libfprint-device-DEBUG: 17:03:06.590: Completing action FPI_DEVICE_ACTION_PROBE in idle! 308s (process:2265): libfprint-device-DEBUG: 17:03:06.590: Not updating temperature model, device can run continuously! 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.591: [goodixmoc] FP_INIT_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.591: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.591: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.592: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.592: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.593: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-goodixmoc-DEBUG: 17:03:06.593: Firmware type: APP 308s (process:2265): libfprint-goodixmoc-DEBUG: 17:03:06.593: Firmware version: 01000274 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.593: [goodixmoc] FP_INIT_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.593: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.593: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.593: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.594: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.594: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.595: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.595: [goodixmoc] FP_INIT_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.595: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.595: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.596: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.596: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.596: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.597: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.597: [goodixmoc] FP_INIT_NUM_STATES completed successfully 308s (process:2265): libfprint-device-DEBUG: 17:03:06.597: Device reported open completion 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.597: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-device-DEBUG: 17:03:06.597: Completing action FPI_DEVICE_ACTION_OPEN in idle! 308s (process:2265): libfprint-device-DEBUG: 17:03:06.597: Not updating temperature model, device can run continuously! 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.597: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.598: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.598: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.598: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.599: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-goodixmoc-DEBUG: 17:03:06.599: Successfully cleared storage 308s (process:2265): libfprint-device-DEBUG: 17:03:06.599: Device reported deletion completion 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.599: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-device-DEBUG: 17:03:06.599: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 308s (process:2265): libfprint-device-DEBUG: 17:03:06.599: Not updating temperature model, device can run continuously! 308s (process:2265): libfprint-device-DEBUG: 17:03:06.600: Not updating temperature model, device can run continuously! 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.600: [goodixmoc] enroll entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.600: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.600: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.600: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.601: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.601: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.601: [goodixmoc] enroll entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.602: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.602: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.602: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.602: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.603: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.603: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.604: [goodixmoc] enroll entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.604: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.604: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.604: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.604: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.605: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.605: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.606: [goodixmoc] enroll entering state 3 308s (process:2265): libfprint-device-DEBUG: 17:03:06.606: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.606: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.606: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.606: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.607: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.607: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.607: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.608: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.608: [goodixmoc] enroll entering state 4 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.608: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.608: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.608: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.609: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.609: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.610: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.610: Device reported enroll progress, reported 1 of 12 have been completed 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.610: [goodixmoc] enroll entering state 5 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.610: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.610: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.611: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.611: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.611: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.612: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.612: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.612: [goodixmoc] enroll entering state 3 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.612: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.612: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.613: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.613: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.613: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.614: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.614: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.614: [goodixmoc] enroll entering state 4 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.614: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.614: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.615: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.615: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.615: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.616: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.616: Device reported enroll progress, reported 2 of 12 have been completed 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.616: [goodixmoc] enroll entering state 5 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.616: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.617: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.617: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.617: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.618: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.618: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.618: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.618: [goodixmoc] enroll entering state 3 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.618: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.619: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.619: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.619: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.619: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.620: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.620: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.620: [goodixmoc] enroll entering state 4 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.620: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.621: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.621: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.621: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.622: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.622: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.622: Device reported enroll progress, reported 3 of 12 have been completed 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.622: [goodixmoc] enroll entering state 5 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.622: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.623: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.623: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.623: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.624: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.624: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.624: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.624: [goodixmoc] enroll entering state 3 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.625: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.625: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.625: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.625: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.626: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.626: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.627: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.627: [goodixmoc] enroll entering state 4 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.627: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.627: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.627: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.627: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.628: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.628: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.629: Device reported enroll progress, reported 4 of 12 have been completed 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.629: [goodixmoc] enroll entering state 5 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.629: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.629: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.629: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.630: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.630: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.630: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.631: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.631: [goodixmoc] enroll entering state 3 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.631: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.631: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.631: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.632: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.632: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.632: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.633: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.633: [goodixmoc] enroll entering state 4 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.633: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.633: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.633: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.634: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.634: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.635: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.635: Device reported enroll progress, reported 5 of 12 have been completed 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.635: [goodixmoc] enroll entering state 5 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.635: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.635: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.635: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.636: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.636: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.637: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.637: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.637: [goodixmoc] enroll entering state 3 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.637: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.637: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.637: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.638: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.638: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.639: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.639: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.639: [goodixmoc] enroll entering state 4 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.639: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.639: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.639: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.640: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.640: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.641: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.641: Device reported enroll progress, reported 6 of 12 have been completed 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.641: [goodixmoc] enroll entering state 5 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.641: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.641: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.642: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.642: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.642: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.643: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.643: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.643: [goodixmoc] enroll entering state 3 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.643: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.643: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.644: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.644: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.644: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.645: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.645: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.645: [goodixmoc] enroll entering state 4 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.645: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.645: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.645: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.646: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.646: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.647: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.647: Device reported enroll progress, reported 7 of 12 have been completed 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.647: [goodixmoc] enroll entering state 5 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.647: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.647: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.648: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.648: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.648: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.649: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.649: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.649: [goodixmoc] enroll entering state 3 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.649: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.649: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.650: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.650: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.650: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.651: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.651: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.651: [goodixmoc] enroll entering state 4 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.651: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.651: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.652: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.652: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.652: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.653: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.653: Device reported enroll progress, reported 8 of 12 have been completed 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.653: [goodixmoc] enroll entering state 5 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.653: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.654: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.654: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.654: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.655: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.655: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.655: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.655: [goodixmoc] enroll entering state 3 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.655: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.656: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.656: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.656: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.657: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.657: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.657: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.657: [goodixmoc] enroll entering state 4 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.657: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.658: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.658: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.658: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.658: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.659: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.659: Device reported enroll progress, reported 9 of 12 have been completed 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.659: [goodixmoc] enroll entering state 5 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.659: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.659: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.660: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.660: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.661: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.661: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.661: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.661: [goodixmoc] enroll entering state 3 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.661: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.662: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.662: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.662: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.663: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.663: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.663: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.663: [goodixmoc] enroll entering state 4 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.663: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.664: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.664: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.664: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.665: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.665: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.665: Device reported enroll progress, reported 10 of 12 have been completed 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.665: [goodixmoc] enroll entering state 5 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.665: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.666: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.666: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.666: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.667: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.667: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.668: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.668: [goodixmoc] enroll entering state 3 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.668: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.668: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.668: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.668: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.669: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.669: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.670: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.670: [goodixmoc] enroll entering state 4 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.670: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.670: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.670: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.671: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.671: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.671: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.672: Device reported enroll progress, reported 11 of 12 have been completed 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.672: [goodixmoc] enroll entering state 5 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.672: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.672: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.672: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.673: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.673: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.674: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.674: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.674: [goodixmoc] enroll entering state 3 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.674: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.674: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.674: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.675: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.675: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.676: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.676: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.676: [goodixmoc] enroll entering state 4 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.676: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.677: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.677: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.677: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.677: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.678: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.678: Device reported enroll progress, reported 12 of 12 have been completed 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.678: [goodixmoc] enroll entering state 6 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.678: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.679: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.679: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.679: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.680: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.680: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.680: [goodixmoc] enroll entering state 7 308s (process:2265): libfprint-goodixmoc-DEBUG: 17:03:06.680: user_id: FP1-00000000-0-00000000-nobody, user_id_len: 30, finger: 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.680: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.681: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.681: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.681: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.682: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.682: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.682: [goodixmoc] enroll entering state 8 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.682: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.683: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.683: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.683: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.684: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.684: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.684: [goodixmoc] enroll completed successfully 308s (process:2265): libfprint-goodixmoc-DEBUG: 17:03:06.684: Enrollment complete! 308s (process:2265): libfprint-device-DEBUG: 17:03:06.684: Device reported enroll completion 308s (process:2265): libfprint-device-DEBUG: 17:03:06.684: Device reported finger status change: FP_FINGER_STATUS_NONE 308s (process:2265): libfprint-device-DEBUG: 17:03:06.684: Print for finger FP_FINGER_UNKNOWN enrolled 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.684: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-device-DEBUG: 17:03:06.684: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 308s (process:2265): libfprint-device-DEBUG: 17:03:06.684: Not updating temperature model, device can run continuously! 308s (process:2265): libfprint-goodixmoc-DEBUG: 17:03:06.685: 142669979: ../libfprint/drivers/goodixmoc/goodix.c:1536 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.685: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.685: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.685: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.686: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.686: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-goodixmoc-DEBUG: 17:03:06.687: Query complete! 308s (process:2265): libfprint-device-DEBUG: 17:03:06.687: Device reported listing completion 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.687: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-device-DEBUG: 17:03:06.687: Completing action FPI_DEVICE_ACTION_LIST in idle! 308s (process:2265): libfprint-device-DEBUG: 17:03:06.687: Not updating temperature model, device can run continuously! 308s (process:2265): libfprint-device-DEBUG: 17:03:06.687: Not updating temperature model, device can run continuously! 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.687: [goodixmoc] verify entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.687: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.687: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.688: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.688: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.688: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.689: [goodixmoc] verify entering state 1 308s (process:2265): libfprint-device-DEBUG: 17:03:06.689: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.689: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.689: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.689: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.690: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.690: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.691: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.691: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.691: [goodixmoc] verify entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.691: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.691: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.691: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.692: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.692: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.693: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-DEBUG: 17:03:06.693: match, score: 28, study: 0 308s (process:2265): libfprint-device-DEBUG: 17:03:06.693: Device reported verify result 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.693: [goodixmoc] verify entering state 3 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.693: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.693: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.694: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.694: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.694: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.695: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.695: [goodixmoc] verify completed successfully 308s (process:2265): libfprint-goodixmoc-DEBUG: 17:03:06.695: Verify complete! 308s (process:2265): libfprint-device-DEBUG: 17:03:06.695: Device reported verify completion 308s (process:2265): libfprint-device-DEBUG: 17:03:06.695: Device reported finger status change: FP_FINGER_STATUS_NONE 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.695: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-device-DEBUG: 17:03:06.695: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 308s (process:2265): libfprint-device-DEBUG: 17:03:06.695: Not updating temperature model, device can run continuously! 308s (process:2265): libfprint-device-DEBUG: 17:03:06.696: Not updating temperature model, device can run continuously! 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.696: [goodixmoc] verify entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.696: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.696: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.697: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.697: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.697: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.698: [goodixmoc] verify entering state 1 308s (process:2265): libfprint-device-DEBUG: 17:03:06.698: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.698: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.698: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.698: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.699: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.699: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.700: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-device-DEBUG: 17:03:06.700: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.700: [goodixmoc] verify entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.700: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.700: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.701: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.701: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.702: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.702: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-DEBUG: 17:03:06.703: match, score: 35, study: 0 308s (process:2265): libfprint-device-DEBUG: 17:03:06.703: Device reported identify result 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.703: [goodixmoc] verify entering state 3 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.703: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.703: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.703: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.703: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.704: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.704: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.705: [goodixmoc] verify completed successfully 308s (process:2265): libfprint-goodixmoc-DEBUG: 17:03:06.705: Verify complete! 308s (process:2265): libfprint-device-DEBUG: 17:03:06.705: Device reported identify completion 308s (process:2265): libfprint-device-DEBUG: 17:03:06.705: Device reported finger status change: FP_FINGER_STATUS_NONE 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.705: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-device-DEBUG: 17:03:06.705: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 308s (process:2265): libfprint-device-DEBUG: 17:03:06.705: Not updating temperature model, device can run continuously! 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.705: [goodixmoc] FP_CMD_NUM_STATES entering state 0 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.706: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.706: [goodixmoc] FP_CMD_NUM_STATES entering state 1 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.707: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.707: [goodixmoc] FP_CMD_NUM_STATES entering state 2 308s (process:2265): libfprint-goodixmoc-DEBUG: 17:03:06.707: Successfully deleted enrolled user 308s (process:2265): libfprint-device-DEBUG: 17:03:06.707: Device reported deletion completion 308s (process:2265): libfprint-SSM-DEBUG: 17:03:06.707: [goodixmoc] FP_CMD_NUM_STATES completed successfully 308s (process:2265): libfprint-device-DEBUG: 17:03:06.707: Completing action FPI_DEVICE_ACTION_DELETE in idle! 308s (process:2265): libfprint-device-DEBUG: 17:03:06.707: Not updating temperature model, device can run continuously! 308s (process:2265): libfprint-device-DEBUG: 17:03:06.708: Device reported close completion 308s (process:2265): libfprint-device-DEBUG: 17:03:06.708: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 308s (process:2265): libfprint-device-DEBUG: 17:03:06.708: Not updating temperature model, device can run continuously! 308s enrolling 308s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xf9955c339540 (FpiDeviceGoodixMoc at 0x1e5e84c0)>, 1, None, None, None) 308s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xf9955c339540 (FpiDeviceGoodixMoc at 0x1e5e84c0)>, 2, None, None, None) 308s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xf9955c339540 (FpiDeviceGoodixMoc at 0x1e5e84c0)>, 3, None, None, None) 308s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xf9955c339540 (FpiDeviceGoodixMoc at 0x1e5e84c0)>, 4, None, None, None) 308s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xf9955c339540 (FpiDeviceGoodixMoc at 0x1e5e84c0)>, 5, None, None, None) 308s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xf9955c339540 (FpiDeviceGoodixMoc at 0x1e5e84c0)>, 6, None, None, None) 308s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xf9955c339540 (FpiDeviceGoodixMoc at 0x1e5e84c0)>, 7, None, None, None) 308s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xf9955c339540 (FpiDeviceGoodixMoc at 0x1e5e84c0)>, 8, None, None, None) 308s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xf9955c339540 (FpiDeviceGoodixMoc at 0x1e5e84c0)>, 9, None, None, None) 308s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xf9955c339540 (FpiDeviceGoodixMoc at 0x1e5e84c0)>, 10, None, None, None) 308s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xf9955c339540 (FpiDeviceGoodixMoc at 0x1e5e84c0)>, 11, None, None, None) 308s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xf9955c339540 (FpiDeviceGoodixMoc at 0x1e5e84c0)>, 12, None, None, None) 308s enroll done 308s listing 308s listing done 308s verifying 308s verify done 308s async identifying 308s indentification_done: 308s deleting 308s delete done 308s ** (umockdev-run:2261): DEBUG: 17:03:06.719: umockdev.vala:150: Removing test bed /tmp/umockdev.1ON0J2 308s (umockdev-run:2261): GLib-DEBUG: 17:03:06.722: unsetenv() is not thread-safe and should not be used after threads are created 308s PASS: libfprint-2/driver-goodixmoc.test 308s Running test: libfprint-2/driver-vfs5011.test 308s ** (umockdev-run:2273): DEBUG: 17:03:06.764: umockdev.vala:123: Created udev test bed /tmp/umockdev.Q55WJ2 308s ** (umockdev-run:2273): DEBUG: 17:03:06.764: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb2/2-6 308s ** (umockdev-run:2273): DEBUG: 17:03:06.765: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb2/2-6 (subsystem usb) 308s ** (umockdev-run:2273): DEBUG: 17:03:06.767: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.Q55WJ2/dev/bus/usb/002/017 308s ** (umockdev-run:2273): DEBUG: 17:03:06.767: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb2 308s ** (umockdev-run:2273): DEBUG: 17:03:06.768: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb2 (subsystem usb) 308s ** (umockdev-run:2273): DEBUG: 17:03:06.769: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.Q55WJ2/dev/bus/usb/002/001 308s ** (umockdev-run:2273): DEBUG: 17:03:06.769: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 308s ** (umockdev-run:2273): DEBUG: 17:03:06.770: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 308s (umockdev-run:2273): GLib-GIO-DEBUG: 17:03:06.771: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 308s (process:2277): libfprint-context-DEBUG: 17:03:06.827: Initializing FpContext (libfprint version 1.94.7+tod1) 308s (process:2277): libfprint-tod-DEBUG: 17:03:06.827: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 308s (process:2277): libfprint-context-DEBUG: 17:03:06.829: No driver found for USB device 1D6B:0002 308s (process:2277): libfprint-device-DEBUG: 17:03:06.829: Device reported probe completion 308s (process:2277): libfprint-device-DEBUG: 17:03:06.829: Completing action FPI_DEVICE_ACTION_PROBE in idle! 308s (process:2277): libfprint-device-DEBUG: 17:03:06.829: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] can(process:2277): libfprint-SSM-DEBUG: 17:03:06.831: [vfs5011] DEV_OPEN_NUM_STATES entering state 0 308s not find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s libusb: error [op_handle_events] cannot find handle for fd 9 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.831: [vfs5011] DEVICE OPEN entering state 0 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.831: Sending vfs5011_cmd_01 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.831: [vfs5011] DEVICE OPEN entering state 1 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.832: Receiving 64 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.832: Got 38 bytes out of 64 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.832: [vfs5011] DEVICE OPEN entering state 2 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.832: Sending vfs5011_cmd_19 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.832: [vfs5011] DEVICE OPEN entering state 3 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.833: Receiving 64 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.833: Got 64 bytes out of 64 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.833: [vfs5011] DEVICE OPEN entering state 4 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.833: Receiving 64 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.833: Got 4 bytes out of 64 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.833: [vfs5011] DEVICE OPEN entering state 5 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.833: Sending vfs5011_init_00 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.834: [vfs5011] DEVICE OPEN entering state 6 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.834: Receiving 64 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.834: Got 6 bytes out of 64 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.834: [vfs5011] DEVICE OPEN entering state 7 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.834: Sending vfs5011_init_01 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.835: [vfs5011] DEVICE OPEN entering state 8 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.835: Receiving 64 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.835: Got 7 bytes out of 64 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.835: [vfs5011] DEVICE OPEN entering state 9 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.835: Sending vfs5011_init_02 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.836: [vfs5011] DEVICE OPEN entering state 10 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.836: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.836: [vfs5011] DEVICE OPEN entering state 11 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.836: Sending vfs5011_cmd_01 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.837: [vfs5011] DEVICE OPEN entering state 12 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.837: Receiving 64 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.837: Got 38 bytes out of 64 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.837: [vfs5011] DEVICE OPEN entering state 13 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.837: Sending vfs5011_cmd_1A 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.838: [vfs5011] DEVICE OPEN entering state 14 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.838: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.838: [vfs5011] DEVICE OPEN entering state 15 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.838: Sending vfs5011_init_03 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.839: [vfs5011] DEVICE OPEN entering state 16 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.839: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.839: [vfs5011] DEVICE OPEN entering state 17 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.839: Sending vfs5011_init_04 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.840: [vfs5011] DEVICE OPEN entering state 18 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.840: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.840: [vfs5011] DEVICE OPEN entering state 19 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.840: Receiving 256 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.840: Got 256 bytes out of 256 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.840: [vfs5011] DEVICE OPEN entering state 20 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.840: Receiving 64 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.841: Got 32 bytes out of 64 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.841: [vfs5011] DEVICE OPEN entering state 21 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.841: Sending vfs5011_cmd_1A 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.841: [vfs5011] DEVICE OPEN entering state 22 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.841: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.842: [vfs5011] DEVICE OPEN entering state 23 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.842: Sending vfs5011_init_05 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.842: [vfs5011] DEVICE OPEN entering state 24 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.842: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.843: [vfs5011] DEVICE OPEN entering state 25 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.843: Sending vfs5011_cmd_01 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.843: [vfs5011] DEVICE OPEN entering state 26 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.843: Receiving 64 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.843: Got 38 bytes out of 64 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.843: [vfs5011] DEVICE OPEN entering state 27 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.843: Sending vfs5011_init_06 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.844: [vfs5011] DEVICE OPEN entering state 28 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.844: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.844: [vfs5011] DEVICE OPEN entering state 29 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.844: Receiving 17216 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.845: Got 17216 bytes out of 17216 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.845: [vfs5011] DEVICE OPEN entering state 30 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.845: Receiving 32 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.845: Got 32 bytes out of 32 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.845: [vfs5011] DEVICE OPEN entering state 31 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.845: Sending vfs5011_init_07 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.845: [vfs5011] DEVICE OPEN entering state 32 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.845: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.846: [vfs5011] DEVICE OPEN entering state 33 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.846: Receiving 45056 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.847: Got 45056 bytes out of 45056 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.847: [vfs5011] DEVICE OPEN entering state 34 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.847: Sending vfs5011_init_08 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.847: [vfs5011] DEVICE OPEN entering state 35 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.847: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.848: [vfs5011] DEVICE OPEN entering state 36 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.848: Receiving 16896 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.848: Got 16896 bytes out of 16896 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.848: [vfs5011] DEVICE OPEN entering state 37 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.848: Sending vfs5011_init_09 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.848: [vfs5011] DEVICE OPEN entering state 38 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.848: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.849: [vfs5011] DEVICE OPEN entering state 39 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.849: Receiving 4928 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.849: Got 4928 bytes out of 4928 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.849: [vfs5011] DEVICE OPEN entering state 40 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.849: Sending vfs5011_init_10 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.850: [vfs5011] DEVICE OPEN entering state 41 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.850: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.850: [vfs5011] DEVICE OPEN entering state 42 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.850: Receiving 5632 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.851: Got 5632 bytes out of 5632 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.851: [vfs5011] DEVICE OPEN entering state 43 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.851: Sending vfs5011_init_11 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.851: [vfs5011] DEVICE OPEN entering state 44 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.851: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.851: [vfs5011] DEVICE OPEN entering state 45 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.851: Receiving 5632 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.852: Got 5632 bytes out of 5632 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.852: [vfs5011] DEVICE OPEN entering state 46 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.852: Sending vfs5011_init_12 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.852: [vfs5011] DEVICE OPEN entering state 47 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.852: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.853: [vfs5011] DEVICE OPEN entering state 48 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.853: Receiving 3328 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.853: Got 3328 bytes out of 3328 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.853: [vfs5011] DEVICE OPEN entering state 49 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.853: Receiving 64 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.854: Got 32 bytes out of 64 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.854: [vfs5011] DEVICE OPEN entering state 50 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.854: Sending vfs5011_init_13 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.854: [vfs5011] DEVICE OPEN entering state 51 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.854: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.854: [vfs5011] DEVICE OPEN entering state 52 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.854: Sending vfs5011_cmd_1A 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.855: [vfs5011] DEVICE OPEN entering state 53 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.855: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.855: [vfs5011] DEVICE OPEN entering state 54 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.855: Sending vfs5011_init_03 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.856: [vfs5011] DEVICE OPEN entering state 55 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.856: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.856: [vfs5011] DEVICE OPEN entering state 56 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.856: Sending vfs5011_init_14 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.856: [vfs5011] DEVICE OPEN entering state 57 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.856: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.857: [vfs5011] DEVICE OPEN entering state 58 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.857: Receiving 4800 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.857: Got 4800 bytes out of 4800 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.857: [vfs5011] DEVICE OPEN entering state 59 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.857: Sending vfs5011_cmd_1A 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.858: [vfs5011] DEVICE OPEN entering state 60 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.858: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.858: [vfs5011] DEVICE OPEN entering state 61 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.858: Sending vfs5011_init_02 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.858: [vfs5011] DEVICE OPEN entering state 62 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.858: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.859: [vfs5011] DEVICE OPEN entering state 63 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.859: Sending vfs5011_cmd_27 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.859: [vfs5011] DEVICE OPEN entering state 64 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.859: Receiving 64 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.860: Got 22 bytes out of 64 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.860: [vfs5011] DEVICE OPEN entering state 65 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.860: Sending vfs5011_cmd_1A 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.860: [vfs5011] DEVICE OPEN entering state 66 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.860: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.861: [vfs5011] DEVICE OPEN entering state 67 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.861: Sending vfs5011_init_15 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.861: [vfs5011] DEVICE OPEN entering state 68 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.861: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.862: [vfs5011] DEVICE OPEN entering state 69 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.862: Sending vfs5011_init_16 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.862: [vfs5011] DEVICE OPEN entering state 70 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.862: Receiving 2368 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.862: Got 2368 bytes out of 2368 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.862: [vfs5011] DEVICE OPEN entering state 71 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.862: Receiving 64 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.863: Got 36 bytes out of 64 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.863: [vfs5011] DEVICE OPEN entering state 72 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.863: Receiving 4800 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.863: Got 4800 bytes out of 4800 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.863: [vfs5011] DEVICE OPEN entering state 73 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.863: Sending vfs5011_init_17 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.864: [vfs5011] DEVICE OPEN entering state 74 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.864: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.864: [vfs5011] DEVICE OPEN entering state 75 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.864: Sending vfs5011_init_18 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.865: [vfs5011] DEVICE OPEN entering state 76 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.865: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.865: [vfs5011] DEVICE OPEN completed successfully 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.865: [vfs5011] DEV_OPEN_NUM_STATES completed successfully 308s (process:2277): libfprint-image_device-DEBUG: 17:03:06.865: Image device open completed 308s (process:2277): libfprint-device-DEBUG: 17:03:06.865: Device reported open completion 308s (process:2277): libfprint-device-DEBUG: 17:03:06.865: Completing action FPI_DEVICE_ACTION_OPEN in idle! 308s (process:2277): libfprint-device-DEBUG: 17:03:06.865: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 308s (process:2277): libfprint-device-DEBUG: 17:03:06.865: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 308s (process:2277): libfprint-image_device-DEBUG: 17:03:06.865: Activating image device 308s (process:2277): libfprint-image_device-DEBUG: 17:03:06.865: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.865: device initialized 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.865: creating ssm 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.865: starting ssm 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.865: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 0 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.865: main_loop: state 0 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.865: [vfs5011] ACTIVATE REQUEST entering state 0 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.865: Sending vfs5011_cmd_04 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.866: ssm done, getting out 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.866: [vfs5011] ACTIVATE REQUEST entering state 1 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.866: Receiving 64 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.866: Got 64 bytes out of 64 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.866: [vfs5011] ACTIVATE REQUEST entering state 2 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.866: Receiving 84032 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.867: Got 176 bytes out of 84032 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.867: [vfs5011] ACTIVATE REQUEST entering state 3 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.867: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.867: [vfs5011] ACTIVATE REQUEST entering state 4 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.867: Sending vfs5011_cmd_1A 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.868: [vfs5011] ACTIVATE REQUEST entering state 5 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.868: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.868: [vfs5011] ACTIVATE REQUEST entering state 6 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.868: Sending vfs5011_prepare_00 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.869: [vfs5011] ACTIVATE REQUEST entering state 7 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.869: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.869: [vfs5011] ACTIVATE REQUEST entering state 8 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.869: Sending vfs5011_cmd_1A 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.869: [vfs5011] ACTIVATE REQUEST entering state 9 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.869: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.870: [vfs5011] ACTIVATE REQUEST entering state 10 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.870: Sending vfs5011_prepare_01 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.870: [vfs5011] ACTIVATE REQUEST entering state 11 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.870: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.871: [vfs5011] ACTIVATE REQUEST entering state 12 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.871: Sending vfs5011_prepare_02 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.871: [vfs5011] ACTIVATE REQUEST entering state 13 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.871: Receiving 2368 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.872: Got 2368 bytes out of 2368 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.872: [vfs5011] ACTIVATE REQUEST entering state 14 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.872: Receiving 64 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.872: Got 36 bytes out of 64 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.872: [vfs5011] ACTIVATE REQUEST entering state 15 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.872: Receiving 4800 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.872: Got 4800 bytes out of 4800 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.872: [vfs5011] ACTIVATE REQUEST entering state 16 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.872: Sending vfs5011_prepare_03 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.873: [vfs5011] ACTIVATE REQUEST entering state 17 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.873: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.873: [vfs5011] ACTIVATE REQUEST entering state 18 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.873: Sending vfs5011_prepare_04 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.874: [vfs5011] ACTIVATE REQUEST entering state 19 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.874: Receiving 2368 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.874: [vfs5011] ACTIVATE REQUEST completed successfully 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.874: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 1 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.874: main_loop: state 1 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.874: capture_init 308s (process:2277): libfprint-image_device-DEBUG: 17:03:06.874: Image device activation completed 308s (process:2277): libfprint-image_device-DEBUG: 17:03:06.874: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 308s (process:2277): libfprint-image_device-DEBUG: 17:03:06.874: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 308s (process:2277): libfprint-device-DEBUG: 17:03:06.874: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.874: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.874: main_loop: state 2 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.874: capture_chunk_async: capture 256 lines, already have 0 308s (process:2277): libfprint-device-DEBUG: 17:03:06.875: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2277): libfprint-image_device-DEBUG: 17:03:06.875: Image device reported finger status: on 308s (process:2277): libfprint-image_device-DEBUG: 17:03:06.875: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.875: process_chunk: got 61440 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.875: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.875: main_loop: state 2 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.875: capture_chunk_async: capture 256 lines, already have 6 308s (process:2277): libfprint-image_device-DEBUG: 17:03:06.875: Image device reported finger status: on 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.875: process_chunk: got 61440 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.875: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.875: main_loop: state 2 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.875: capture_chunk_async: capture 256 lines, already have 25 308s (process:2277): libfprint-image_device-DEBUG: 17:03:06.876: Image device reported finger status: on 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.876: process_chunk: got 61440 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.876: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.876: main_loop: state 2 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.876: capture_chunk_async: capture 256 lines, already have 54 308s (process:2277): libfprint-image_device-DEBUG: 17:03:06.877: Image device reported finger status: on 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.877: process_chunk: got 61440 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.877: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.877: main_loop: state 2 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.877: capture_chunk_async: capture 256 lines, already have 89 308s (process:2277): libfprint-image_device-DEBUG: 17:03:06.877: Image device reported finger status: on 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.877: process_chunk: got 61440 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.877: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.877: main_loop: state 2 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.877: capture_chunk_async: capture 256 lines, already have 117 308s (process:2277): libfprint-image_device-DEBUG: 17:03:06.878: Image device reported finger status: on 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.878: process_chunk: got 61440 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.878: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.878: main_loop: state 2 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.878: capture_chunk_async: capture 256 lines, already have 144 308s (process:2277): libfprint-image_device-DEBUG: 17:03:06.878: Image device reported finger status: on 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.878: process_chunk: got 61440 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.879: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.879: main_loop: state 2 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.879: capture_chunk_async: capture 256 lines, already have 180 308s (process:2277): libfprint-image_device-DEBUG: 17:03:06.879: Image device reported finger status: on 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.879: process_chunk: got 61440 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.879: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.879: main_loop: state 2 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.879: capture_chunk_async: capture 256 lines, already have 273 308s (process:2277): libfprint-image_device-DEBUG: 17:03:06.880: Image device reported finger status: on 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.880: process_chunk: got 61440 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.880: process_chunk: got 50 empty lines, finishing 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.880: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 3 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.880: main_loop: state 3 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.881: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 4 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.881: main_loop: state 4 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.881: [vfs5011] PREPARE CAPTURE entering state 0 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.881: Sending vfs5011_cmd_04 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.882: [vfs5011] PREPARE CAPTURE entering state 1 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.882: Receiving 64 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.882: Got 64 bytes out of 64 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.882: [vfs5011] PREPARE CAPTURE entering state 2 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.882: Receiving 84032 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.883: Got 176 bytes out of 84032 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.883: [vfs5011] PREPARE CAPTURE entering state 3 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.883: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.883: [vfs5011] PREPARE CAPTURE entering state 4 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.883: Sending vfs5011_cmd_1A 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.883: [vfs5011] PREPARE CAPTURE entering state 5 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.883: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.884: [vfs5011] PREPARE CAPTURE entering state 6 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.884: Sending vfs5011_prepare_00 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.884: [vfs5011] PREPARE CAPTURE entering state 7 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.884: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.885: [vfs5011] PREPARE CAPTURE entering state 8 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.885: Sending vfs5011_cmd_1A 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.885: [vfs5011] PREPARE CAPTURE entering state 9 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.885: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.886: [vfs5011] PREPARE CAPTURE entering state 10 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.886: Sending vfs5011_prepare_01 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.886: [vfs5011] PREPARE CAPTURE entering state 11 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.886: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.886: [vfs5011] PREPARE CAPTURE entering state 12 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.886: Sending vfs5011_prepare_02 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.887: [vfs5011] PREPARE CAPTURE entering state 13 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.887: Receiving 2368 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.887: Got 2368 bytes out of 2368 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.887: [vfs5011] PREPARE CAPTURE entering state 14 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.887: Receiving 64 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.888: Got 36 bytes out of 64 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.888: [vfs5011] PREPARE CAPTURE entering state 15 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.888: Receiving 4800 bytes 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.888: Got 4800 bytes out of 4800 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.888: [vfs5011] PREPARE CAPTURE entering state 16 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.888: Sending vfs5011_prepare_03 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.888: [vfs5011] PREPARE CAPTURE entering state 17 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.889: Receiving 64 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.889: [vfs5011] PREPARE CAPTURE entering state 18 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.889: Sending vfs5011_prepare_04 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.889: [vfs5011] PREPARE CAPTURE entering state 19 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.889: Receiving 2368 bytes 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.890: [vfs5011] PREPARE CAPTURE completed successfully 308s (process:2277): libfprint-SSM-DEBUG: 17:03:06.890: [vfs5011] DEV_ACTIVATE_NUM_STATES completed successfully 308s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.890: finishing 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 1709917386890363 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 1 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 5 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 4 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 4 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 3 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 3 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 5 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 4 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 27 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 27 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 27 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 27 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 28 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 5 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 28 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 29 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 29 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 29 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 29 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 28 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 28 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 29 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 28 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 30 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 29 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 30 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 5 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 5 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 30 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 30 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 30 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 30 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 30 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 4 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 4 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 29 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 30 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 29 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 9 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 30 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 30 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 30 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 30 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 30 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 9 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 9 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 9 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 9 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 9 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 9 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 9 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 29 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 29 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 11 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 9 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 9 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 9 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 9 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 9 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 30 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 9 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 27 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 26 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 5 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 4 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 2 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: offsets_filtered: 1709917386890866 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 5 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 5 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 5 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 5 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 5 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 27 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 27 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 27 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 27 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 27 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 27 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 27 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 28 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 28 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 28 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 28 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 28 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 28 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 28 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 28 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 28 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 29 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 29 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 29 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 29 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 29 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 29 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 28 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 28 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 28 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 6 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 7 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.890: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 308s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 9 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 9 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 9 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 9 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 9 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 9 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 9 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 9 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 9 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 9 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 9 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 9 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.891: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.892: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.892: 8 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.892: 7 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.892: 7 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.892: 7 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.892: 7 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.892: 7 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.892: 7 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.892: 7 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.892: 7 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.892: 7 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.892: 7 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.892: 7 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.892: 7 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.892: 7 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.892: 7 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.892: 7 309s (process:2277): libfprint-assembling-DEBUG: 17:03:06.892: 2 309s (process:2277): libfprint-vfs5011-DEBUG: 17:03:06.893: Image captured, committing 309s (process:2277): libfprint-image_device-DEBUG: 17:03:06.893: Image device captured an image 309s (process:2277): libfprint-image_device-DEBUG: 17:03:06.894: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 309s (process:2277): libfprint-device-DEBUG: 17:03:06.894: Device reported finger status change: FP_FINGER_STATUS_PRESENT 309s (process:2277): libfprint-device-DEBUG: 17:03:06.894: Device reported finger status change: FP_FINGER_STATUS_NONE 309s (process:2277): libfprint-image_device-DEBUG: 17:03:06.894: Image device reported finger status: off 309s (process:2277): libfprint-image_device-DEBUG: 17:03:06.894: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 309s (process:2277): libfprint-image_device-DEBUG: 17:03:06.894: Deactivating image device 309s (process:2277): libfprint-image_device-DEBUG: 17:03:06.894: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 309s (process:2277): libfprint-image_device-DEBUG: 17:03:06.894: Image device deactivation completed 309s (process:2277): libfprint-image_device-DEBUG: 17:03:06.894: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 309s (process:2277): libfprint-image-DEBUG: 17:03:06.921: Minutiae scan completed in 0.027010 secs 309s (process:2277): libfprint-device-DEBUG: 17:03:06.921: Device reported capture completion 309s (process:2277): libfprint-device-DEBUG: 17:03:06.921: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 309s (process:2277): libfprint-device-DEBUG: 17:03:06.921: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 309s (process:2277): libfprint-image_device-DEBUG: 17:03:06.922: Image device close completed 309s (process:2277): libfprint-device-DEBUG: 17:03:06.922: Device reported close completion 309s (process:2277): libfprint-device-DEBUG: 17:03:06.922: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 309s (process:2277): libfprint-device-DEBUG: 17:03:06.922: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 309s ** (umockdev-run:2273): DEBUG: 17:03:06.995: umockdev.vala:150: Removing test bed /tmp/umockdev.Q55WJ2 309s (umockdev-run:2273): GLib-DEBUG: 17:03:06.999: unsetenv() is not thread-safe and should not be used after threads are created 309s Comparing PNGs /tmp/libfprint-umockdev-test-banbfm2u/capture.png and /usr/share/installed-tests/libfprint-2/vfs5011/capture.png 309s PASS: libfprint-2/driver-vfs5011.test 309s Running test: libfprint-2/driver-upektc_img.test 309s ** (umockdev-run:2286): DEBUG: 17:03:07.058: umockdev.vala:123: Created udev test bed /tmp/umockdev.U39BK2 309s ** (umockdev-run:2286): DEBUG: 17:03:07.058: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3 309s ** (umockdev-run:2286): DEBUG: 17:03:07.060: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3 (subsystem usb) 309s ** (umockdev-run:2286): DEBUG: 17:03:07.062: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.U39BK2/dev/bus/usb/001/003 309s ** (umockdev-run:2286): DEBUG: 17:03:07.062: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1/1-1 309s ** (umockdev-run:2286): DEBUG: 17:03:07.063: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1a.0/usb1/1-1 (subsystem usb) 309s ** (umockdev-run:2286): DEBUG: 17:03:07.065: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.U39BK2/dev/bus/usb/001/002 309s ** (umockdev-run:2286): DEBUG: 17:03:07.065: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1 309s ** (umockdev-run:2286): DEBUG: 17:03:07.066: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1a.0/usb1 (subsystem usb) 309s ** (umockdev-run:2286): DEBUG: 17:03:07.068: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.U39BK2/dev/bus/usb/001/001 309s ** (umockdev-run:2286): DEBUG: 17:03:07.068: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1a.0 309s ** (umockdev-run:2286): DEBUG: 17:03:07.068: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1a.0 (subsystem pci) 309s (process:2290): libfprint-context-DEBUG: 17:03:07.115: Initializing FpContext (libfprint version 1.94.7+tod1) 309s (process:2290): libfprint-tod-DEBUG: 17:03:07.115: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 309s (process:2290): libfprint-context-DEBUG: 17:03:07.117: No driver found for USB device 8087:0020 309s (process:2290): libfprint-context-DEBUG: 17:03:07.117: No driver found for USB device 1D6B:0002 309s (process:2290): libfprint-device-DEBUG: 17:03:07.118: Device reported probe completion 309s (process:2290): libfprint-device-DEBUG: 17:03:07.118: Completing action FPI_DEVICE_ACTION_PROBE in idle! 309s (process:2290): libfprint-device-DEBUG: 17:03:07.118: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s (process:2290): libfprint-image_device-DEBUG: 17:03:07.121: Image device open completed 309s (process:2290): libfprint-device-DEBUG: 17:03:07.121: Device reported open completion 309s (process:2290): libfprint-device-DEBUG: 17:03:07.121: Completing action FPI_DEVICE_ACTION_OPEN in idle! 309s (process:2290): libfprint-device-DEBUG: 17:03:07.121: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s (process:2290): libfprint-device-DEBUG: 17:03:07.121: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s (process:2290): libfprint-image_device-DEBUG: 17:03:07.121: Activating image device 309s (process:2290): libfprint-image_device-DEBUG: 17:03:07.121: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.121: [upektc_img] ACTIVATE_NUM_STATES entering state 0 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.122: [upektc_img] ACTIVATE_NUM_STATES entering state 1 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.122: [upektc_img] ACTIVATE_NUM_STATES entering state 2 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.123: [upektc_img] ACTIVATE_NUM_STATES entering state 3 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.123: [upektc_img] ACTIVATE_NUM_STATES entering state 4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.123: [upektc_img] ACTIVATE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.124: [upektc_img] ACTIVATE_NUM_STATES entering state 6 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.124: [upektc_img] ACTIVATE_NUM_STATES entering state 7 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.125: [upektc_img] ACTIVATE_NUM_STATES entering state 8 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.125: [upektc_img] ACTIVATE_NUM_STATES entering state 9 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.126: [upektc_img] ACTIVATE_NUM_STATES entering state 10 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.126: [upektc_img] ACTIVATE_NUM_STATES entering state 11 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.127: Sensor type : TCS4x, width x height: 192 x 512 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.127: [upektc_img] ACTIVATE_NUM_STATES completed successfully 309s (process:2290): libfprint-image_device-DEBUG: 17:03:07.127: Image device activation completed 309s (process:2290): libfprint-image_device-DEBUG: 17:03:07.127: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 309s (process:2290): libfprint-image_device-DEBUG: 17:03:07.127: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 309s (process:2290): libfprint-device-DEBUG: 17:03:07.127: Device reported finger status change: FP_FINGER_STATUS_NEEDED 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.127: [upektc_img] CAPTURE_NUM_STATES entering state 0 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.127: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.128: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.128: 18th byte is 0c 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.128: [upektc_img] CAPTURE_NUM_STATES entering state 3 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.128: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.129: request completed, len: 0040 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.129: [upektc_img] CAPTURE_NUM_STATES entering state 4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.129: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.130: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.130: 18th byte is 00 309s (process:2290): libfprint-device-DEBUG: 17:03:07.130: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.130: [upektc_img] CAPTURE_NUM_STATES entering state 3 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.130: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.131: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.131: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.131: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.131: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.131: request completed, len: 07c4 309s (process:2290): libfprint-image_device-DEBUG: 17:03:07.131: Image device reported finger status: on 309s (process:2290): libfprint-image_device-DEBUG: 17:03:07.131: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.131: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.132: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.132: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.132: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.132: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.132: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.132: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.132: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.133: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.133: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.133: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.133: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.133: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.134: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.134: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.134: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.135: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.135: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.135: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.135: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.135: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.135: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.135: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.136: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.136: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.136: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.136: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.136: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.136: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.137: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.137: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.137: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.137: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.137: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.138: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.138: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.138: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.138: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.138: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.138: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.138: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.139: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.139: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.139: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.140: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.140: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.140: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.140: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.140: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.140: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.141: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.141: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.141: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.141: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.141: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.141: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.141: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.142: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.142: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.142: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.142: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.142: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.143: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.143: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.143: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.143: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.144: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.144: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.144: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.144: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.144: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.144: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.145: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.145: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.145: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.145: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.145: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.145: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.146: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.146: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.146: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.146: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.146: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.147: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.147: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.147: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.147: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.147: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.147: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.147: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.148: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.148: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.148: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.149: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.149: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.149: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.149: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.149: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.149: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.150: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.150: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.150: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.150: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.150: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.151: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.151: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.151: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.151: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.151: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.151: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.151: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.152: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.152: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.152: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.153: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.153: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.153: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.153: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.153: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.153: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.154: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.154: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.154: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.154: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.154: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.154: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.155: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.155: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.155: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.155: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.155: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.155: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.156: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.156: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.156: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.157: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.157: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.157: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.157: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.157: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.157: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.158: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.158: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.158: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.158: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.158: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.159: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.159: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.159: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.159: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.159: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.159: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.159: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.160: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.160: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.160: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.161: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.161: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.161: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.161: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.161: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.161: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.162: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.162: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.162: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.162: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.162: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.162: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.162: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.163: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.163: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.163: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.163: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.163: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.164: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.164: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.164: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.165: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.165: response_size is 2052, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.165: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.165: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.165: request completed, len: 07c4 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.165: [upektc_img] CAPTURE_NUM_STATES entering state 5 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.166: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.166: request completed, len: 0040 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.166: response_size is 186, actual_length is 64 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.166: Waiting for rest of transfer 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.166: [upektc_img] CAPTURE_NUM_STATES entering state 1 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.166: request completed, len: 007a 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.166: Image size is 55296 309s (process:2290): libfprint-image_device-DEBUG: 17:03:07.166: Image device captured an image 309s (process:2290): libfprint-image_device-DEBUG: 17:03:07.171: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 309s (process:2290): libfprint-device-DEBUG: 17:03:07.171: Device reported finger status change: FP_FINGER_STATUS_PRESENT 309s (process:2290): libfprint-device-DEBUG: 17:03:07.171: Device reported finger status change: FP_FINGER_STATUS_NONE 309s (process:2290): libfprint-image_device-DEBUG: 17:03:07.171: Image device reported finger status: off 309s (process:2290): libfprint-image_device-DEBUG: 17:03:07.171: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 309s (process:2290): libfprint-image_device-DEBUG: 17:03:07.171: Deactivating image device 309s (process:2290): libfprint-image_device-DEBUG: 17:03:07.171: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.171: [upektc_img] CAPTURE_NUM_STATES completed successfully 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.171: [upektc_img] DEACTIVATE_NUM_STATES entering state 0 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.171: [upektc_img] DEACTIVATE_NUM_STATES entering state 1 309s (process:2290): libfprint-SSM-DEBUG: 17:03:07.171: [upektc_img] DEACTIVATE_NUM_STATES completed successfully 309s (process:2290): libfprint-upektc_img-DEBUG: 17:03:07.171: Deactivate completed 309s (process:2290): libfprint-image_device-DEBUG: 17:03:07.171: Image device deactivation completed 309s (process:2290): libfprint-image_device-DEBUG: 17:03:07.171: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 309s (process:2290): libfprint-image-DEBUG: 17:03:07.183: Minutiae scan completed in 0.016498 secs 309s (process:2290): libfprint-device-DEBUG: 17:03:07.184: Device reported capture completion 309s (process:2290): libfprint-device-DEBUG: 17:03:07.184: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 309s (process:2290): libfprint-device-DEBUG: 17:03:07.184: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 309s (process:2290): libfprint-image_device-DEBUG: 17:03:07.184: Image device close completed 309s (process:2290): libfprint-device-DEBUG: 17:03:07.184: Device reported close completion 309s (process:2290): libfprint-device-DEBUG: 17:03:07.184: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 309s (process:2290): libfprint-device-DEBUG: 17:03:07.184: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 309s ** (umockdev-run:2286): DEBUG: 17:03:07.253: umockdev.vala:150: Removing test bed /tmp/umockdev.U39BK2 309s (umockdev-run:2286): GLib-DEBUG: 17:03:07.257: unsetenv() is not thread-safe and should not be used after threads are created 309s Comparing PNGs /tmp/libfprint-umockdev-test-0h7h_r05/capture.png and /usr/share/installed-tests/libfprint-2/upektc_img/capture.png 309s PASS: libfprint-2/driver-upektc_img.test 309s Running test: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_current.test 309s TAP version 13 309s # random seed: R02S0b274c5b55253ec2977875d08013ee9c 309s 1..14 309s # Start of device tests 309s # Start of async tests 309s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 309s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 309s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf37da6a62580, GType is 205396061238992 309s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 309s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 309s # libfprint-context-DEBUG: created 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 309s # 309s # libfprint-device-DEBUG: Device reported probe completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 309s # 309s # libfprint-device-DEBUG: Device reported open completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 309s # 309s # libfprint-device-DEBUG: Device reported close completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s ok 1 /device/async/open 309s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 309s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 309s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf37da6a62580, GType is 205396061238992 309s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 309s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 309s # libfprint-context-DEBUG: created 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 309s # 309s # libfprint-device-DEBUG: Device reported probe completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 309s # 309s # libfprint-device-DEBUG: Device reported open completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 309s # 309s # libfprint-device-DEBUG: Device reported close completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s ok 2 /device/async/close 309s # End of async tests 309s # Start of sync tests 309s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 309s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 309s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf37da6a62580, GType is 205396061238992 309s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 309s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 309s # libfprint-context-DEBUG: created 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 309s # 309s # libfprint-device-DEBUG: Device reported probe completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 309s # 309s # libfprint-device-DEBUG: Device reported open completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 309s # 309s # libfprint-device-DEBUG: Device reported close completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s ok 3 /device/sync/open 309s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 309s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 309s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf37da6a62580, GType is 205396061238992 309s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 309s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 309s # libfprint-context-DEBUG: created 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 309s # 309s # libfprint-device-DEBUG: Device reported probe completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 309s # 309s # libfprint-device-DEBUG: Device reported open completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 309s # 309s # libfprint-device-DEBUG: Device reported close completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s ok 4 /device/sync/close 309s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 309s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 309s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf37da6a62580, GType is 205396061238992 309s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 309s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 309s # libfprint-context-DEBUG: created 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 309s # 309s # libfprint-device-DEBUG: Device reported probe completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 309s # 309s # libfprint-device-DEBUG: Device reported open completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 309s # 309s # libfprint-device-DEBUG: Device reported close completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s ok 5 /device/sync/get_driver 309s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 309s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 309s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf37da6a62580, GType is 205396061238992 309s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 309s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 309s # libfprint-context-DEBUG: created 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 309s # 309s # libfprint-device-DEBUG: Device reported probe completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 309s # 309s # libfprint-device-DEBUG: Device reported open completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 309s # 309s # libfprint-device-DEBUG: Device reported close completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s ok 6 /device/sync/get_device_id 309s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 309s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 309s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf37da6a62580, GType is 205396061238992 309s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 309s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 309s # libfprint-context-DEBUG: created 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 309s # 309s # libfprint-device-DEBUG: Device reported probe completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 309s # 309s # libfprint-device-DEBUG: Device reported open completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 309s # 309s # libfprint-device-DEBUG: Device reported close completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s ok 7 /device/sync/get_name 309s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 309s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 309s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf37da6a62580, GType is 205396061238992 309s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 309s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 309s # libfprint-context-DEBUG: created 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 309s # 309s # libfprint-device-DEBUG: Device reported probe completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 309s # 309s # libfprint-device-DEBUG: Device reported open completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 309s # 309s # libfprint-device-DEBUG: Device reported close completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s ok 8 /device/sync/get_scan_type 309s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 309s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 309s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf37da6a62580, GType is 205396061238992 309s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 309s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 309s # libfprint-context-DEBUG: created 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 309s # 309s # libfprint-device-DEBUG: Device reported probe completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 309s # 309s # libfprint-device-DEBUG: Device reported open completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 309s # 309s # libfprint-device-DEBUG: Device reported close completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s ok 9 /device/sync/get_nr_enroll_stages 309s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 309s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 309s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf37da6a62580, GType is 205396061238992 309s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 309s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 309s # libfprint-context-DEBUG: created 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 309s # 309s # libfprint-device-DEBUG: Device reported probe completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 309s # 309s # libfprint-device-DEBUG: Device reported open completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 309s # 309s # libfprint-device-DEBUG: Device reported close completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s ok 10 /device/sync/supports_identify 309s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 309s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 309s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf37da6a62580, GType is 205396061238992 309s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 309s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 309s # libfprint-context-DEBUG: created 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 309s # 309s # libfprint-device-DEBUG: Device reported probe completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 309s # 309s # libfprint-device-DEBUG: Device reported open completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 309s # 309s # libfprint-device-DEBUG: Device reported close completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s ok 11 /device/sync/supports_capture 309s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 309s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 309s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf37da6a62580, GType is 205396061238992 309s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 309s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 309s # libfprint-context-DEBUG: created 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 309s # 309s # libfprint-device-DEBUG: Device reported probe completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 309s # 309s # libfprint-device-DEBUG: Device reported open completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 309s # 309s # libfprint-device-DEBUG: Device reported close completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s ok 12 /device/sync/has_storage 309s # Start of open tests 309s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 309s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 309s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf37da6a62580, GType is 205396061238992 309s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 309s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 309s # libfprint-context-DEBUG: created 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 309s # 309s # libfprint-device-DEBUG: Device reported probe completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 309s # 309s # libfprint-device-DEBUG: Device reported open completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 309s # 309s # libfprint-device-DEBUG: Device reported close completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s ok 13 /device/sync/open/notify 309s # End of open tests 309s # Start of close tests 309s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.7+tod1) 309s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 309s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf37da6a62580, GType is 205396061238992 309s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 309s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 309s # libfprint-context-DEBUG: created 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 309s # 309s # libfprint-device-DEBUG: Device reported probe completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 309s # 309s # libfprint-device-DEBUG: Device reported open completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 309s # 309s # libfprint-device-DEBUG: Device reported close completion 309s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 309s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s ok 14 /device/sync/close/notify 309s # End of close tests 309s # End of sync tests 309s # End of device tests 309s PASS: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_current.test 309s Running test: libfprint-2/driver-aes2501.test 309s ** (umockdev-run:2331): DEBUG: 17:03:07.335: umockdev.vala:123: Created udev test bed /tmp/umockdev.5V3FK2 309s ** (umockdev-run:2331): DEBUG: 17:03:07.335: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 309s ** (umockdev-run:2331): DEBUG: 17:03:07.336: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 309s ** (umockdev-run:2331): DEBUG: 17:03:07.338: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.5V3FK2/dev/bus/usb/001/044 309s ** (umockdev-run:2331): DEBUG: 17:03:07.338: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 309s ** (umockdev-run:2331): DEBUG: 17:03:07.339: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 309s ** (umockdev-run:2331): DEBUG: 17:03:07.341: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.5V3FK2/dev/bus/usb/001/001 309s ** (umockdev-run:2331): DEBUG: 17:03:07.341: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 309s ** (umockdev-run:2331): DEBUG: 17:03:07.341: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 309s (process:2335): libfprint-context-DEBUG: 17:03:07.388: Initializing FpContext (libfprint version 1.94.7+tod1) 309s (process:2335): libfprint-tod-DEBUG: 17:03:07.389: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 309s (process:2335): libfprint-context-DEBUG: 17:03:07.390: No driver found for USB device 1D6B:0002 309s (process:2335): libfprint-device-DEBUG: 17:03:07.390: Device reported probe completion 309s (process:2335): libfprint-device-DEBUG: 17:03:07.390: Completing action FPI_DEVICE_ACTION_PROBE in idle! 309s (process:2335): libfprint-device-DEBUG: 17:03:07.390: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s libusb: error [op_handle_events] cannot find handle for fd 9 309s (process:2335): libfprint-image_device-DEBUG: 17:03:07.394: Image device open completed 309s (process:2335): libfprint-device-DEBUG: 17:03:07.394: Device reported open completion 309s (process:2335): libfprint-device-DEBUG: 17:03:07.394: Completing action FPI_DEVICE_ACTION_OPEN in idle! 309s (process:2335): libfprint-device-DEBUG: 17:03:07.394: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s (process:2335): libfprint-device-DEBUG: 17:03:07.394: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 309s (process:2335): libfprint-image_device-DEBUG: 17:03:07.394: Activating image device 309s (process:2335): libfprint-image_device-DEBUG: 17:03:07.394: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 309s (process:2335): libfprint-SSM-DEBUG: 17:03:07.394: [aes2501] ACTIVATE_NUM_STATES entering state 0 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.394: write 38 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.395: all registers written 309s (process:2335): libfprint-SSM-DEBUG: 17:03:07.395: [aes2501] ACTIVATE_NUM_STATES entering state 1 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.395: read data 1 309s (process:2335): libfprint-SSM-DEBUG: 17:03:07.396: [aes2501] ACTIVATE_NUM_STATES entering state 2 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.396: write 7 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.396: all registers written 309s (process:2335): libfprint-SSM-DEBUG: 17:03:07.396: [aes2501] ACTIVATE_NUM_STATES entering state 3 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.396: 143381673: ../libfprint/drivers/aes2501.c:140 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.396: write 1 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.397: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.397: reg 0xaf = 20 309s (process:2335): libfprint-SSM-DEBUG: 17:03:07.397: [aes2501] ACTIVATE_NUM_STATES entering state 5 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.397: write 7 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.397: all registers written 309s (process:2335): libfprint-SSM-DEBUG: 17:03:07.397: [aes2501] ACTIVATE_NUM_STATES entering state 6 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.397: write 16 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.398: all registers written 309s (process:2335): libfprint-SSM-DEBUG: 17:03:07.398: [aes2501] ACTIVATE_NUM_STATES completed successfully 309s (process:2335): libfprint-image_device-DEBUG: 17:03:07.398: Image device activation completed 309s (process:2335): libfprint-image_device-DEBUG: 17:03:07.398: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 309s (process:2335): libfprint-image_device-DEBUG: 17:03:07.398: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 309s (process:2335): libfprint-device-DEBUG: 17:03:07.398: Device reported finger status change: FP_FINGER_STATUS_NEEDED 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.398: 143383321: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.398: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.399: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.399: 143384811: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.399: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.401: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.401: 143386406: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.401: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.402: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.403: 143387909: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.403: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.404: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.404: 143389465: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.404: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.405: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.406: 143391056: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.406: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.407: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.407: 143392555: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.407: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.408: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.409: 143394095: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.409: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.410: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.410: 143395585: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.410: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.411: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.412: 143397224: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.412: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.413: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.413: 143398879: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.413: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.415: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.415: 143400443: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.415: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.416: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.417: 143401949: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.417: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.418: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.418: 143403433: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.418: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.419: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.420: 143405012: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.420: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.421: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.421: 143406469: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.421: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.422: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.423: 143408011: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.423: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.424: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.424: 143409558: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.424: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.425: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.426: 143411105: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.426: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.427: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.427: 143412669: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.427: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.428: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.429: 143414100: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.429: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.430: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.430: 143415596: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.430: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.431: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.432: 143417167: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.432: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.433: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.433: 143418711: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.433: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.434: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.435: 143420094: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.435: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.436: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.436: 143421620: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.436: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.437: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.438: 143423054: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.438: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.439: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.439: 143424655: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.439: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.440: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.441: 143426198: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.441: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.442: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.442: 143427668: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.442: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.443: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.444: 143429200: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.444: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.445: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.445: 143430727: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.445: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.446: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.447: 143432304: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.447: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.448: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.448: 143433816: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.448: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.449: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.450: 143435218: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.450: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.451: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.451: 143436776: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.451: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.452: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.453: 143438308: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.453: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.454: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.455: 143440032: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.455: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.456: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.456: 143441616: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.456: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.457: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.458: 143443119: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.458: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.459: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.459: 143444608: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.459: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.460: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.461: 143446292: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.461: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.462: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.463: 143447985: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.463: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.464: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.464: 143449524: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.464: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.465: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.466: 143451038: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.466: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.467: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.467: 143452494: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.467: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.468: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.469: 143454077: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.469: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.470: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.470: 143455623: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.470: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.471: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.472: 143457220: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.472: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.473: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.473: 143458628: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.473: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.474: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.475: 143460081: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.475: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.476: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.476: 143461547: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.476: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.477: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.478: 143463053: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.478: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.479: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.479: 143464604: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.479: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.480: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.481: 143466146: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.481: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.482: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.482: 143467746: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.482: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.484: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.484: 143469396: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.484: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.485: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.485: 143470880: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.485: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.487: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.487: 143472384: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.487: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.488: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.489: 143473922: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.489: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.490: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.490: 143475305: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.490: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.491: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.491: 143476829: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.491: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.493: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.493: 143478255: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.493: write 23 regs 309s (process:2335): libfprint-device-DEBUG: 17:03:07.494: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.494: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.495: 143479944: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.495: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.496: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.496: 143481435: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.496: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.497: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.498: 143483000: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.498: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.499: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.499: 143484548: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.499: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.500: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.501: 143486029: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.501: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.502: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.502: 143487670: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.502: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.504: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.504: 143489347: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.504: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.505: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.505: 143490894: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.505: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.507: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.507: 143492526: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.507: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.508: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.509: 143494063: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.509: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.510: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.510: 143495481: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.510: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.511: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.512: 143496969: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.512: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.513: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.513: 143498471: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.513: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.514: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.515: 143500020: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.515: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.516: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.516: 143501648: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.516: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.517: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.518: 143503174: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.518: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.519: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.519: 143504821: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.519: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.520: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.521: 143506304: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.521: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.522: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.523: 143507916: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.523: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.524: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.524: 143509393: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.524: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.525: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.526: 143510967: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.526: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.527: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.527: 143512517: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.527: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.528: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.529: 143514184: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.529: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.530: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.530: 143515899: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.531: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.532: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.532: 143517492: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.532: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.533: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.534: 143519042: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.534: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.535: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.535: 143520665: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.535: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.536: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.537: 143522278: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.537: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.538: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.539: 143523908: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.539: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.540: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.540: 143525566: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.540: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.541: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.542: 143527105: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.542: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.543: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.543: 143528717: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.543: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.544: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.545: 143530213: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.545: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.546: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.546: 143531572: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.546: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.547: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.548: 143533039: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.548: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.549: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.549: 143534566: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.549: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.550: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.551: 143536147: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.551: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.552: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.552: 143537730: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.552: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.553: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.554: 143539333: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.554: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.555: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.555: 143540781: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.555: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.557: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.557: 143542405: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.557: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.558: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.559: 143544018: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.559: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.560: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.560: 143545595: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.560: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.561: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.562: 143546977: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.562: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.563: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.563: 143548539: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.563: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.564: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.565: 143550151: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.565: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.566: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.566: 143551753: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.566: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.567: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.568: 143553190: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.568: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.569: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.569: 143554731: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.569: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.570: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.571: 143556220: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.571: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.572: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.572: 143557817: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.572: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.574: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.574: 143559352: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.574: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.575: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.576: 143560938: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.576: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.577: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.577: 143562420: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.577: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.578: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.579: 143564014: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.579: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.580: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.580: 143565646: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.580: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.581: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.582: 143567191: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.582: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.583: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.583: 143568829: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.583: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.584: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.585: 143570289: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.585: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.586: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.587: 143571975: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.587: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.588: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.588: 143573494: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.588: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.589: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.590: 143575070: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.590: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.591: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.591: 143576684: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.591: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.592: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.593: 143578301: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.593: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.594: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.595: 143579975: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.595: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.596: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.596: 143581708: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.596: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.597: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.598: 143583359: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.598: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.599: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.600: 143585026: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.600: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.601: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.601: 143586543: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.601: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.602: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.603: 143588163: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.603: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.604: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.604: 143589818: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.604: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.606: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.606: 143591470: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.606: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.607: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.608: 143593129: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.608: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.609: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.609: 143594715: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.609: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.610: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.611: 143596318: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.611: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.612: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.613: 143597931: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.613: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.614: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.614: 143599694: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.614: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.615: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.616: 143601128: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.616: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.617: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.617: 143602743: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.617: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.618: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.619: 143604308: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.619: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.620: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.620: 143605743: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.620: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.622: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.622: 143607331: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.622: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.623: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.623: 143608879: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.623: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.625: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.625: 143610366: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.625: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.626: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.626: 143611870: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.626: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.628: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.628: 143613482: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.628: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.629: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.630: 143615020: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.630: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.631: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.631: 143616691: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.631: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.632: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.633: 143618181: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.633: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.634: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.634: 143619740: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.634: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.636: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.636: 143621350: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.636: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.637: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.637: 143622878: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.637: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.638: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.639: 143624284: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.639: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.640: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.640: 143625890: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.641: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.642: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.642: 143627435: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.642: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.643: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.644: 143629025: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.644: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.645: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.645: 143630481: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.645: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.646: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.647: 143632022: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.647: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.648: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.648: 143633509: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.648: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.649: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.650: 143635126: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.650: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.651: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.651: 143636703: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.651: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.652: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.653: 143638250: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.653: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.654: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.655: 143640018: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.655: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.656: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.656: 143641628: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.656: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.657: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.658: 143643236: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.658: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.659: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.660: 143644924: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.660: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.661: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.661: 143646557: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.661: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.662: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.663: 143648092: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.663: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.664: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.664: 143649632: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.664: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.665: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.666: 143651277: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.666: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.667: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.667: 143652845: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.667: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.669: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.669: 143654544: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.669: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.670: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.671: 143656172: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.671: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.672: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.672: 143657876: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.672: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.674: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.674: 143659428: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.674: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.675: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.676: 143661010: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.676: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.677: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.677: 143662623: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.677: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.679: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.679: 143664331: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.679: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.680: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.681: 143665935: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.681: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.682: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.682: 143667532: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.682: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.683: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.684: 143668971: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.684: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.685: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.685: 143670457: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.685: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.686: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.687: 143672064: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.687: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.688: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.688: 143673710: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.688: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.689: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.690: 143675253: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.690: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.691: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.691: 143676751: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.691: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.692: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.693: 143678250: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.693: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.694: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.694: 143679836: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.694: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.696: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.696: 143681420: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.696: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.697: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.697: 143682883: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.698: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.699: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.699: 143684510: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.699: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.700: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.701: 143686125: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.701: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.702: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.702: 143687712: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.702: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.704: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.704: 143689374: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.704: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.705: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.706: 143690949: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.706: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.707: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.707: 143692517: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.707: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.708: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.709: 143694058: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.709: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.710: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.710: 143695612: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.710: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.711: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.712: 143697225: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.712: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.713: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.713: 143698780: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.713: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.715: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.715: 143700248: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.715: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.716: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.716: 143701826: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.716: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.718: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.718: 143703471: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.718: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.719: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.720: 143705013: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.720: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.721: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.721: 143706528: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.721: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.722: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.723: 143708027: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.723: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.724: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.724: 143709556: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.724: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.725: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.726: 143711090: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.726: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.727: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.727: 143712861: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.727: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.729: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.729: 143714591: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.729: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.730: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.731: 143716318: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.731: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.732: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.733: 143717987: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.733: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.734: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.734: 143719609: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.734: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.735: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.736: 143721327: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.736: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.737: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.738: 143722967: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.738: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.739: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.739: 143724646: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.739: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.740: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.741: 143726340: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.741: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.742: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.743: 143728015: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.743: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.744: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.744: 143729578: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.744: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.745: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.746: 143731223: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.746: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.747: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.747: 143732778: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.747: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.749: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.749: 143734333: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.749: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.750: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.750: 143735812: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.750: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.752: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.752: 143737421: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.752: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.753: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.753: 143738868: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.753: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.755: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.755: 143740360: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.755: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.756: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.756: 143741877: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.756: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.758: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.758: 143743487: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.758: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.759: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.760: 143745200: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.760: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.761: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.761: 143746737: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.761: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.762: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.763: 143748355: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.763: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.764: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.764: 143749829: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.764: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.766: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.766: 143751341: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.766: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.767: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.767: 143752872: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.767: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.769: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.769: 143754418: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.769: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.770: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.770: 143755828: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.770: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.772: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.772: 143757315: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.772: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.773: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.774: 143758931: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.774: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.775: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.775: 143760492: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.775: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.776: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.777: 143762068: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.777: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.778: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.778: 143763738: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.778: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.779: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.780: 143765271: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.780: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.781: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.782: 143766907: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.782: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.783: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.783: 143768446: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.783: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.784: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.785: 143769946: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.785: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.786: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.786: 143771604: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.786: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.787: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.788: 143773242: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.788: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.789: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.789: 143774796: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.789: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.790: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.791: 143776333: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.791: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.792: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.793: 143778077: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.793: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.794: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.794: 143779724: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.794: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.795: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.796: 143781351: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.796: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.797: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.798: 143783003: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.798: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.799: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.799: 143784610: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.799: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.800: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.801: 143786240: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.801: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.802: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.802: 143787849: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.802: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.804: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.804: 143789558: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.804: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.805: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.806: 143791174: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.806: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.807: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.807: 143792784: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.807: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.809: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.809: 143794367: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.809: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.810: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.811: 143796135: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.811: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.812: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.812: 143797679: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.812: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.813: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.814: 143799173: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.814: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.815: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.815: 143800708: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.815: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.816: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.817: 143802165: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.817: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.818: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.818: 143803753: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.818: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.819: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.820: 143805259: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.820: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.821: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.821: 143806731: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.821: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.823: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.823: 143808307: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.823: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.824: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.824: 143809797: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.824: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.826: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.826: 143811343: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.826: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.827: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.827: 143812863: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.827: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.829: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.829: 143814364: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.829: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.830: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.831: 143815956: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.831: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.832: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.832: 143817516: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.832: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.833: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.834: 143819211: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.834: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.835: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.835: 143820876: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.835: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.837: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.837: 143822539: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.837: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.838: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.839: 143824052: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.839: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.840: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.840: 143825632: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.840: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.841: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.842: 143827151: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.842: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.843: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.843: 143828701: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.843: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.844: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.845: 143830314: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.845: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.846: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.846: 143831780: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.846: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.847: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.848: 143833293: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.848: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.849: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.849: 143834852: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.849: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.851: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.851: 143836401: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.851: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.852: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.853: 143837942: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.853: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.854: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.854: 143839515: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.854: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.855: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.856: 143841253: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.856: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.857: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.857: 143842807: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.857: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.858: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.859: 143844285: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.859: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.860: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.860: 143845841: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.860: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.862: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.862: 143847495: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.862: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.863: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.864: 143849153: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.864: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.865: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.865: 143850884: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.866: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.867: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.867: 143852558: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.867: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.868: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.869: 143854103: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.869: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.870: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.870: 143855734: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.870: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.871: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.872: 143857207: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.872: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.873: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.874: 143858905: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.874: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.875: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.875: 143860575: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.875: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.876: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.877: 143862271: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.877: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.878: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.878: 143863754: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.878: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.879: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.880: 143865353: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.880: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.881: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.882: 143866981: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.882: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.883: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.883: 143868635: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.883: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.884: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.885: 143870173: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.885: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.886: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.886: 143871743: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.886: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.887: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.888: 143873273: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.888: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.889: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.889: 143874820: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.889: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.890: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.891: 143876294: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.891: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.892: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.893: 143877913: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.893: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.894: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.894: 143879488: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.894: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.895: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.896: 143881082: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.896: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.897: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.897: 143882589: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.897: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.898: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.899: 143884133: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.899: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.900: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.900: 143885723: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.900: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.901: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.902: 143887275: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.902: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.903: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.903: 143888801: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.903: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.905: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.905: 143890295: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.905: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.906: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.906: 143891775: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.906: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.907: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.908: 143893287: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.908: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.909: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.909: 143894764: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.909: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.910: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.911: 143896311: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.911: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.912: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.912: 143897827: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.912: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.914: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.914: 143899373: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.914: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.915: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.915: 143900885: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.915: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.917: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.917: 143902352: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.917: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.918: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.919: 143903965: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.919: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.920: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.920: 143905520: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.920: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.921: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.922: 143907201: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.922: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.923: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.923: 143908718: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.923: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.924: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.925: 143910313: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.925: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.926: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.927: 143911922: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.927: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.928: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.928: 143913591: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.928: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.929: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.930: 143915231: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.930: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.931: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.931: 143916854: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.931: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.933: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.933: 143918457: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.933: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.934: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.935: 143920079: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.935: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.936: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.936: 143921725: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.936: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.938: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.938: 143923374: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.938: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.939: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.940: 143925009: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.940: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.941: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.941: 143926706: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.941: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.943: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.943: 143928492: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.943: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.944: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.945: 143930149: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.945: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.946: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.946: 143931718: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.946: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.947: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.948: 143933369: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.948: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.949: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.950: 143935062: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.950: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.951: all registers written 309s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.951: 143936729: ../libfprint/drivers/aes2501.c:310 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.951: write 23 regs 309s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.952: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.953: 143938232: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.953: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.954: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.954: 143939831: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.954: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.955: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.956: 143941342: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.956: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.957: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.957: 143942765: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.957: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.958: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.959: 143944274: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.959: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.960: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.960: 143945729: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.960: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.961: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.962: 143947209: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.962: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.963: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.963: 143948747: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.963: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.964: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.965: 143950219: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.965: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.966: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.966: 143951840: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.966: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.968: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.968: 143953342: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.968: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.969: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.969: 143954784: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.969: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.971: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.971: 143956490: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.971: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.972: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.973: 143958000: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.973: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.974: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.974: 143959557: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.974: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.975: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.976: 143961224: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.976: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.977: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.977: 143962627: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.977: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.978: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.979: 143964163: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.979: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.980: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.980: 143965745: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.980: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.981: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.982: 143967273: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.982: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.983: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.983: 143968813: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.983: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.985: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.985: 143970442: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.985: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.986: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.987: 143971996: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.987: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.988: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.988: 143973596: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.988: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.989: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.990: 143975212: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.990: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.991: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.991: 143976735: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.991: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.993: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.993: 143978533: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.993: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.994: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.995: 143980216: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.995: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.996: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.996: 143981857: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.996: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.998: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:07.998: 143983535: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.998: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:07.999: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.000: 143985065: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.000: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.001: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.001: 143986562: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.001: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.002: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.003: 143988144: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.003: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.004: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.004: 143989599: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.004: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.005: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.006: 143991151: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.006: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.007: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.007: 143992585: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.007: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.008: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.009: 143994066: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.009: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.010: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.010: 143995668: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.010: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.011: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.012: 143997155: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.012: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.013: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.013: 143998768: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.013: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.014: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.015: 144000360: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.015: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.016: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.017: 144001942: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.017: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.018: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.018: 144003492: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.018: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.019: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.020: 144005051: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.020: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.021: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.021: 144006703: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.021: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.022: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.023: 144008312: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.023: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.024: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.024: 144009888: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.025: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.026: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.026: 144011502: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.026: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.027: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.028: 144013117: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.028: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.029: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.029: 144014665: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.029: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.030: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.031: 144016274: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.031: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.032: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.032: 144017885: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.033: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.034: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.034: 144019328: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.034: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.035: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.035: 144020866: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.035: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.037: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.037: 144022454: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.037: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.038: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.038: 144023882: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.039: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.040: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.040: 144025359: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.040: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.041: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.042: 144026984: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.042: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.043: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.043: 144028521: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.043: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.044: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.045: 144030074: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.045: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.046: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.046: 144031652: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.046: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.047: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.048: 144033111: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.048: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.049: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.049: 144034618: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.049: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.050: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.051: 144036148: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.051: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.052: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.052: 144037634: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.052: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.053: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.054: 144039185: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.054: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.055: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.055: 144040689: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.055: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.056: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.057: 144042291: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.057: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.058: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.058: 144043819: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.058: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.059: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.060: 144045222: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.060: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.061: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.061: 144046802: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.061: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.063: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.063: 144048361: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.063: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.064: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.065: 144049972: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.065: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.066: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.066: 144051591: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.066: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.067: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.068: 144053290: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.068: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.069: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.070: 144054944: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.070: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.071: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.071: 144056485: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.071: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.072: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.073: 144058101: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.073: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.074: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.074: 144059675: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.074: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.075: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.076: 144061238: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.076: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.077: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.077: 144062766: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.077: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.078: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.079: 144064295: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.079: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.080: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.080: 144065895: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.080: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.082: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.082: 144067287: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.082: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.083: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.084: 144068914: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.084: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.085: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.085: 144070352: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.085: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.086: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.086: 144071784: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.086: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.088: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.088: 144073412: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.088: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.089: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.090: 144075086: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.090: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.091: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.091: 144076692: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.091: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.092: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.093: 144078362: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.093: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.094: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.095: 144080049: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.095: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.096: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.096: 144081694: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.096: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.097: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.098: 144083275: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.098: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.099: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.099: 144084807: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.099: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.101: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.101: 144086450: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.101: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.102: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.103: 144087935: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.103: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.104: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.104: 144089459: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.104: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.105: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.106: 144091073: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.106: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.107: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.107: 144092602: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.107: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.108: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.109: 144094266: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.109: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.110: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.110: 144095851: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.110: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.112: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.112: 144097414: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.112: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.113: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.114: 144098974: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.114: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.115: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.115: 144100574: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.115: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.116: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.117: 144101995: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.117: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.118: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.118: 144103513: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.118: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.119: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.120: 144105021: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.120: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.121: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.121: 144106571: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.121: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.122: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.123: 144108206: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.123: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.124: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.124: 144109756: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.124: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.125: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.126: 144111332: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.126: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.127: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.128: 144113012: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.128: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.129: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.129: 144114711: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.129: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.130: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.131: 144116326: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.131: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.132: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.132: 144117840: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.132: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.134: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.134: 144119553: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.134: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.135: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.136: 144121184: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.136: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.137: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.137: 144122758: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.137: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.138: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.139: 144124256: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.139: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.140: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.140: 144125656: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.140: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.141: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.142: 144127158: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.142: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.143: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.143: 144128693: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.143: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.144: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.145: 144130205: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.145: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.146: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.146: 144131818: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.146: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.147: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.148: 144133367: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.148: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.149: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.149: 144134846: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.149: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.150: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.151: 144136214: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.151: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.152: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.152: 144137701: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.152: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.153: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.154: 144139121: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.154: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.155: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.155: 144140676: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.155: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.156: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.157: 144142151: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.157: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.158: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.158: 144143600: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.158: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.159: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.160: 144145092: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.160: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.161: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.161: 144146832: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.161: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.163: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.163: 144148618: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.163: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.164: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.165: 144150118: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.165: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.166: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.166: 144151735: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.166: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.168: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.168: 144153366: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.168: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.169: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.170: 144155119: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.170: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.171: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.171: 144156749: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.171: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.172: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.173: 144158174: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.173: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.174: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.174: 144159801: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.174: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.176: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.176: 144161408: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.176: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.177: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.178: 144162991: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.178: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.179: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.179: 144164580: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.179: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.180: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.181: 144166135: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.181: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.182: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.182: 144167611: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.182: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.183: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.184: 144169147: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.184: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.185: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.185: 144170597: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.185: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.186: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.187: 144172092: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.187: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.188: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.188: 144173634: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.188: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.189: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.190: 144175121: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.190: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.191: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.191: 144176682: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.191: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.192: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.193: 144178252: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.193: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.194: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.195: 144179934: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.195: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.196: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.196: 144181558: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.196: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.197: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.198: 144183079: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.198: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.199: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.199: 144184800: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.199: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.201: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.201: 144186431: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.201: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.202: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.203: 144187956: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.203: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.204: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.204: 144189462: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.204: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.205: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.206: 144191105: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.206: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.207: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.207: 144192536: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.207: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.208: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.209: 144193936: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.209: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.210: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.210: 144195446: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.210: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.211: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.212: 144196974: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.212: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.213: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.213: 144198445: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.213: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.214: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.215: 144200005: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.215: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.216: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.216: 144201526: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.216: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.217: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.218: 144203015: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.218: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.219: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.219: 144204541: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.219: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.220: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.221: 144205994: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.221: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.222: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.222: 144207519: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.222: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.223: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.224: 144209105: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.224: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.225: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.225: 144210576: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.225: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.226: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.227: 144212159: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.227: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.228: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.228: 144213871: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.229: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.230: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.230: 144215623: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.230: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.231: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.232: 144217260: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.232: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.233: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.233: 144218867: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.233: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.235: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.235: 144220512: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.235: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.236: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.237: 144222149: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.237: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.238: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.239: 144223916: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.239: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.240: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.240: 144225608: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.240: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.241: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.242: 144227119: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.242: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.243: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.243: 144228606: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.243: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.244: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.245: 144230110: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.245: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.246: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.246: 144231695: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.246: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.247: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.248: 144233276: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.248: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.249: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.249: 144234852: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.249: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.251: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.251: 144236493: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.251: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.252: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.253: 144238062: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.253: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.254: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.254: 144239576: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.254: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.255: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.256: 144241178: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.256: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.257: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.257: 144242613: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.257: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.258: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.259: 144244170: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.259: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.260: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.260: 144245655: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.260: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.261: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.262: 144247328: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.262: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.263: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.264: 144249026: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.264: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.265: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.265: 144250764: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.265: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.266: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.267: 144252265: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.267: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.268: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.268: 144253865: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.268: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.270: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.270: 144255461: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.270: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.271: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.272: 144257074: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.272: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.273: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.273: 144258698: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.273: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.274: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.275: 144260241: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.275: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.276: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.276: 144261760: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.276: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.277: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.278: 144263292: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.278: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.279: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.279: 144264831: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.279: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.281: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.281: 144266348: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.281: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.282: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.282: 144267846: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.282: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.283: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.284: 144269273: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.284: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.285: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.285: 144270774: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.285: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.286: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.287: 144272179: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.287: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.288: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.288: 144273580: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.288: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.289: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.290: 144275181: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.290: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.291: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.291: 144276747: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.291: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.292: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.293: 144278262: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.293: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.294: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.294: 144279757: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.294: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.295: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.296: 144281355: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.296: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.297: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.298: 144282987: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.298: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.299: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.299: 144284552: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.299: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.300: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.301: 144286303: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.301: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.302: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.303: 144287950: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.303: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.304: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.304: 144289648: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.304: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.305: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.306: 144291187: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.306: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.307: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.307: 144292817: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.307: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.309: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.309: 144294425: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.309: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.310: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.311: 144296060: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.311: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.312: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.312: 144297597: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.312: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.313: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.314: 144299205: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.314: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.315: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.315: 144300722: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.315: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.316: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.317: 144302307: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.317: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.318: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.318: 144303881: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.318: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.320: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.320: 144305473: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.320: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.321: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.322: 144306937: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.322: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.323: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.323: 144308563: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.323: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.324: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.325: 144310033: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.325: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.326: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.326: 144311626: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.326: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.327: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.328: 144313280: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.328: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.329: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.330: 144314906: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.330: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.331: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.331: 144316450: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.331: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.332: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.333: 144318117: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.333: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.334: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.334: 144319683: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.334: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.335: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.336: 144321248: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.336: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.337: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.337: 144322756: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.337: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.339: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.339: 144324350: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.339: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.340: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.340: 144325789: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.340: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.342: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.342: 144327417: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.342: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.343: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.343: 144328892: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.343: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.345: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.345: 144330430: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.345: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.346: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.347: 144331973: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.347: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.348: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.348: 144333546: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.348: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.349: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.350: 144334975: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.350: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.351: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.351: 144336634: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.351: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.352: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.353: 144338255: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.353: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.354: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.354: 144339886: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.354: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.356: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.356: 144341454: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.356: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.357: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.358: 144342946: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.358: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.359: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.359: 144344545: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.359: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.360: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.361: 144346036: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.361: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.362: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.362: 144347771: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.362: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.364: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.364: 144349398: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.364: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.365: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.365: 144350783: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.365: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.367: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.367: 144352477: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.367: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.368: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.369: 144354228: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.369: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.370: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.370: 144355807: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.370: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.372: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.372: 144357466: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.372: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.373: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.374: 144359027: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.374: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.375: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.375: 144360616: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.375: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.376: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.377: 144362178: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.377: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.378: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.378: 144363606: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.378: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.379: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.380: 144365073: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.380: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.381: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.381: 144366557: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.381: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.382: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.383: 144368025: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.383: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.384: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.384: 144369683: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.384: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.385: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.386: 144371253: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.386: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.387: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.388: 144373013: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.388: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.389: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.389: 144374471: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.389: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.390: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.391: 144376060: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.391: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.392: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.393: 144377965: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.393: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.394: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.394: 144379581: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.394: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.395: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.396: 144381226: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.396: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.397: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.397: 144382885: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.397: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.399: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.399: 144384454: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.399: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.400: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.401: 144386164: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.401: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.402: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.402: 144387902: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.403: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.404: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.404: 144389580: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.404: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.405: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.406: 144391009: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.406: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.407: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.407: 144392582: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.407: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.408: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.409: 144394137: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.409: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.410: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.410: 144395718: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.410: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.411: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.412: 144397213: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.412: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.413: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.413: 144398692: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.413: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.414: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.415: 144400150: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.415: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.416: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.416: 144401670: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.416: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.417: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.418: 144403223: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.418: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.419: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.419: 144404828: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.419: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.421: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.421: 144406380: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.421: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.422: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.422: 144407770: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.422: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.423: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.424: 144409300: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.424: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.425: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.425: 144410771: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.425: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.427: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.427: 144412352: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.427: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.428: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.429: 144413984: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.429: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.430: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.430: 144415429: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.430: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.431: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.432: 144416963: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.432: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.433: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.433: 144418616: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.433: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.434: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.435: 144420180: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.435: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.436: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.436: 144421765: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.436: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.438: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.438: 144423468: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.438: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.439: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.440: 144425138: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.440: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.441: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.441: 144426780: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.441: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.443: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.443: 144428351: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.443: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.444: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.445: 144430074: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.445: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.446: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.446: 144431644: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.446: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.447: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.448: 144433257: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.448: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.449: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.449: 144434817: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.449: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.450: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.451: 144436258: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.451: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.452: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.452: 144437813: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.452: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.454: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.454: 144439433: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.454: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.455: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.456: 144440959: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.456: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.457: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.457: 144442485: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.457: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.458: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.459: 144444092: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.459: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.460: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.460: 144445758: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.460: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.462: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.462: 144447384: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.462: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.463: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.463: 144448893: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.463: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.464: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.465: 144450434: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.465: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.466: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.467: 144452042: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.467: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.468: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.468: 144453637: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.468: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.469: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.470: 144455304: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.470: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.471: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.472: 144456916: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.472: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.473: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.473: 144458659: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.473: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.474: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.475: 144460262: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.475: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.476: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.476: 144461824: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.476: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.478: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.478: 144463443: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.478: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.479: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.480: 144464964: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.480: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.481: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.481: 144466488: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.481: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.482: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.483: 144468100: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.483: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.484: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.484: 144469774: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.484: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.485: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.486: 144471183: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.486: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.487: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.487: 144472676: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.487: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.488: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.489: 144474268: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.489: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.490: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.490: 144475724: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.490: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.491: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.492: 144477250: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.492: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.493: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.493: 144478706: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.493: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.494: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.495: 144480346: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.495: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.496: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.497: 144481930: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.497: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.498: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.498: 144483566: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.498: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.499: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.500: 144485196: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.500: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.501: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.502: 144486916: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.502: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.503: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.503: 144488477: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.503: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.504: all registers written 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.505: 144490177: ../libfprint/drivers/aes2501.c:310 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.505: write 23 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.506: all registers written 310s (process:2335): libfprint-device-DEBUG: 17:03:08.506: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2335): libfprint-image_device-DEBUG: 17:03:08.506: Image device reported finger status: on 310s (process:2335): libfprint-image_device-DEBUG: 17:03:08.506: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.506: 144491804: ../libfprint/drivers/aes2501.c:581 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.506: [aes2501] CAPTURE_NUM_STATES entering state 0 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.506: write 26 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.508: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.508: [aes2501] CAPTURE_NUM_STATES entering state 1 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.508: [aes2501] CAPTURE_NUM_STATES entering state 2 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.508: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.508: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.508: [aes2501] CAPTURE_NUM_STATES entering state 3 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.509: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.509: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.509: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.509: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.510: sum=5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.510: ADREFHI is 50 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.510: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.510: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.510: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.510: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.511: sum=8 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.511: ADREFHI is 48 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.511: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.511: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.511: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.511: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.512: sum=19 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.512: ADREFHI is 40 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.512: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.512: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.512: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.512: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.512: sum=60 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.512: ADREFHI is 38 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.512: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.512: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.513: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.513: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.513: sum=123 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.513: ADREFHI is 30 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.513: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.513: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.514: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.514: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.514: sum=226 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.514: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.514: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.514: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.515: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.515: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.515: sum=461 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.515: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.515: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.515: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.516: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.516: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.516: sum=466 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.516: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.516: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.516: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.516: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.516: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.517: sum=465 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.517: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.517: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.517: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.517: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.517: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.518: sum=620 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.518: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.518: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.518: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.518: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.518: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.518: sum=629 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.518: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.519: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.519: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.519: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.519: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.519: sum=615 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.519: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.519: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.519: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.520: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.520: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.520: sum=585 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.520: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.520: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.520: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.521: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.521: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.521: sum=581 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.521: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.521: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.521: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.522: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.522: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.522: sum=418 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.522: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.522: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.522: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.523: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.523: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.523: sum=406 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.523: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.523: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.523: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.524: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.524: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.524: sum=389 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.524: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.524: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.524: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.524: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.524: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.525: sum=388 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.525: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.525: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.525: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.525: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.525: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.526: sum=393 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.526: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.526: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.526: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.526: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.526: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.527: sum=389 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.527: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.527: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.527: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.527: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.527: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.527: sum=379 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.527: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.527: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.527: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.528: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.528: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.528: sum=361 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.528: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.528: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.528: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.529: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.529: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.529: sum=356 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.529: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.529: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.529: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.529: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.529: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.530: sum=193 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.530: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.530: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.530: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.530: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.530: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.531: sum=178 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.531: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.531: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.531: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.531: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.531: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.532: sum=164 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.532: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.532: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.532: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.532: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.532: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.533: sum=157 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.533: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.533: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.533: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.533: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.533: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.533: sum=152 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.533: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.533: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.533: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.534: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.534: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.534: sum=154 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.534: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.534: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.534: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.535: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.535: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.535: sum=157 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.535: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.535: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.535: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.536: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.536: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.536: sum=161 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.536: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.536: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.536: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.536: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.536: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.537: sum=161 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.537: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.537: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.537: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.537: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.537: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.538: sum=161 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.538: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.538: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.538: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.538: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.538: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.539: sum=162 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.539: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.539: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.539: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.539: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.539: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.540: sum=166 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.540: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.540: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.540: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.540: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.540: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.540: sum=143 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.540: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.540: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.540: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.541: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.541: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.541: sum=106 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.541: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.541: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.541: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.542: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.542: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.542: sum=74 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.542: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.542: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.542: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.543: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.543: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.543: sum=51 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.543: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.543: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.543: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.544: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.544: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.544: sum=40 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.544: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.544: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.544: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.544: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.544: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.545: sum=39 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.545: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.545: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.545: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.545: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.545: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.546: sum=19 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.546: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.546: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.546: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.546: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.546: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.547: sum=13 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.547: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.547: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.547: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.547: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.547: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.547: sum=5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.547: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.547: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.547: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.548: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.548: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.548: sum=2 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.548: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.548: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.548: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.549: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.549: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.549: sum=0 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.549: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.549: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.549: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.550: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.550: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.550: sum=0 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.550: ADREFHI is 28 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.550: [aes2501] CAPTURE_NUM_STATES entering state 4 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.550: write 7 regs 310s (process:2335): libfprint-aeslib-DEBUG: 17:03:08.550: all registers written 310s (process:2335): libfprint-SSM-DEBUG: 17:03:08.550: [aes2501] CAPTURE_NUM_STATES entering state 5 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.551: sum=0 310s (process:2335): libfprint-aes2501-DEBUG: 17:03:08.551: ADREFHI is 28 310s (process:2335): libfprint-assembling-DEBUG: 17:03:08.761: calc delta completed in 0.210078 secs 310s (process:2335): libfprint-assembling-DEBUG: 17:03:08.966: calc delta completed in 0.204317 secs 310s (process:2335): libfprint-assembling-DEBUG: 17:03:08.966: errors: 53228 rev: 72653 311s (process:2335): libfprint-assembling-DEBUG: 17:03:09.179: calc delta completed in 0.213260 secs 311s (process:2335): libfprint-assembling-DEBUG: 17:03:09.179: height is 102 311s (process:2335): libfprint-image_device-DEBUG: 17:03:09.181: Image device captured an image 311s (process:2335): libfprint-image_device-DEBUG: 17:03:09.182: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 311s (process:2335): libfprint-device-DEBUG: 17:03:09.182: Device reported finger status change: FP_FINGER_STATUS_PRESENT 311s (process:2335): libfprint-device-DEBUG: 17:03:09.182: Device reported finger status change: FP_FINGER_STATUS_NONE 311s (process:2335): libfprint-image_device-DEBUG: 17:03:09.182: Image device reported finger status: off 311s (process:2335): libfprint-image_device-DEBUG: 17:03:09.182: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 311s (process:2335): libfprint-image_device-DEBUG: 17:03:09.182: Deactivating image device 311s (process:2335): libfprint-image_device-DEBUG: 17:03:09.182: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 311s (process:2335): libfprint-SSM-DEBUG: 17:03:09.182: [aes2501] CAPTURE_NUM_STATES completed successfully 311s (process:2335): libfprint-aes2501-DEBUG: 17:03:09.182: 145167824: ../libfprint/drivers/aes2501.c:547 311s (process:2335): libfprint-aes2501-DEBUG: 17:03:09.182: 145167828: ../libfprint/drivers/aes2501.c:820 311s (process:2335): libfprint-image_device-DEBUG: 17:03:09.182: Image device deactivation completed 311s (process:2335): libfprint-image_device-DEBUG: 17:03:09.183: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 311s (process:2335): libfprint-image-DEBUG: 17:03:09.195: Minutiae scan completed in 0.012359 secs 311s (process:2335): libfprint-device-DEBUG: 17:03:09.196: Device reported capture completion 311s (process:2335): libfprint-device-DEBUG: 17:03:09.196: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 311s (process:2335): libfprint-device-DEBUG: 17:03:09.196: Updated temperature model after 1.70 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s (process:2335): libfprint-image_device-DEBUG: 17:03:09.196: Image device close completed 311s (process:2335): libfprint-device-DEBUG: 17:03:09.196: Device reported close completion 311s (process:2335): libfprint-device-DEBUG: 17:03:09.197: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s (process:2335): libfprint-device-DEBUG: 17:03:09.197: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s ** (umockdev-run:2331): DEBUG: 17:03:09.240: umockdev.vala:150: Removing test bed /tmp/umockdev.5V3FK2 311s (umockdev-run:2331): GLib-DEBUG: 17:03:09.244: unsetenv() is not thread-safe and should not be used after threads are created 311s Comparing PNGs /tmp/libfprint-umockdev-test-7o57ih9z/capture.png and /usr/share/installed-tests/libfprint-2/aes2501/capture.png 311s PASS: libfprint-2/driver-aes2501.test 311s Running test: libfprint-2/fpi-device.test 311s TAP version 13 311s # random seed: R02S1173697023a08eebc7afb1cf71aae5ef 311s 1..97 311s # Start of driver tests 311s ok 1 /driver/get_driver 311s ok 2 /driver/get_device_id 311s ok 3 /driver/get_name 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s ok 4 /driver/is_open 311s ok 5 /driver/get_nr_enroll_stages 311s ok 6 /driver/set_nr_enroll_stages 311s ok 7 /driver/supports_identify 311s ok 8 /driver/supports_capture 311s ok 9 /driver/has_storage 311s ok 10 /driver/do_not_support_identify 311s ok 11 /driver/do_not_support_capture 311s ok 12 /driver/has_not_storage 311s ok 13 /driver/get_usb_device 311s ok 14 /driver/get_virtual_env 311s ok 15 /driver/get_driver_data 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 311s # 311s # libfprint-device-DEBUG: Device reported probe completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s ok 16 /driver/initial_features 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Probed device name in action FPI_DEVICE_ACTION_PROBE 311s # 311s # libfprint-device-DEBUG: Device reported probe completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s ok 17 /driver/probe 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s ok 18 /driver/open 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s ok 19 /driver/close 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 311s # 311s # libfprint-device-DEBUG: Device reported enroll completion 311s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s ok 20 /driver/enroll 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 311s # 311s # libfprint-device-DEBUG: Device reported verify result 311s # libfprint-device-DEBUG: Device reported verify completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s ok 21 /driver/verify 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 311s # 311s # libfprint-device-DEBUG: Device reported identify result 311s # libfprint-device-DEBUG: Device reported identify completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s ok 22 /driver/identify 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 311s # 311s # libfprint-device-DEBUG: Device reported capture completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s ok 23 /driver/capture 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 311s # 311s # libfprint-device-DEBUG: Device reported listing completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s ok 24 /driver/list 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 311s # 311s # libfprint-device-DEBUG: Device reported deletion completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s ok 25 /driver/delete 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 311s # 311s # libfprint-device-DEBUG: Device reported deletion completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s ok 26 /driver/clear_storage 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 311s # 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 311s # 311s # libfprint-device-DEBUG: Device reported deletion completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s ok 27 /driver/cancel 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 311s # 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 311s # 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 311s # 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 311s # 311s # libfprint-device-DEBUG: Device reported verify result 311s # libfprint-device-DEBUG: Device reported verify completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s ok 28 /driver/critical 311s ok 29 /driver/get_current_action 311s ok 30 /driver/timeout 311s ok 31 /driver/error_types 311s ok 32 /driver/retry_error_types 311s # Start of get_scan_type tests 311s ok 33 /driver/get_scan_type/press 311s ok 34 /driver/get_scan_type/swipe 311s # End of get_scan_type tests 311s # Start of set_scan_type tests 311s ok 35 /driver/set_scan_type/press 311s ok 36 /driver/set_scan_type/swipe 311s # End of set_scan_type tests 311s # Start of finger_status tests 311s ok 37 /driver/finger_status/inactive 311s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 311s ok 38 /driver/finger_status/waiting 311s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 311s ok 39 /driver/finger_status/present 311s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 311s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 311s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 311s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 311s ok 40 /driver/finger_status/changes 311s # End of finger_status tests 311s # Start of features tests 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 311s # 311s # libfprint-device-DEBUG: Device reported probe completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s ok 41 /driver/features/probe_updates 311s # End of features tests 311s # Start of initial_features tests 311s ok 42 /driver/initial_features/none 311s ok 43 /driver/initial_features/no_capture 311s ok 44 /driver/initial_features/no_verify 311s ok 45 /driver/initial_features/no_identify 311s ok 46 /driver/initial_features/no_storage 311s ok 47 /driver/initial_features/no_list 311s ok 48 /driver/initial_features/no_delete 311s ok 49 /driver/initial_features/no_clear 311s # End of initial_features tests 311s # Start of probe tests 311s # libfprint-device-DEBUG: Device reported probe completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s ok 50 /driver/probe/error 311s # libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE 311s # libfprint-device-DEBUG: Device reported probe completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s ok 51 /driver/probe/action_error 311s # End of probe tests 311s # Start of open tests 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s ok 52 /driver/open/error 311s # End of open tests 311s # Start of close tests 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s ok 53 /driver/close/error 311s # End of close tests 311s # Start of enroll tests 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 311s # 311s # libfprint-device-DEBUG: Device reported enroll completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s ok 54 /driver/enroll/error 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Device reported enroll progress, reported 1193480561 of 923877494 have been completed 311s # libfprint-device-DEBUG: Device reported enroll progress, reported 2079915857 of 923877494 have been completed 311s # libfprint-device-DEBUG: Device reported enroll progress, reported 1488080774 of 923877494 have been completed 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 311s # 311s # libfprint-device-DEBUG: Device reported enroll completion 311s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s ok 55 /driver/enroll/progress 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 311s # 311s # libfprint-device-DEBUG: Device reported enroll completion 311s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s ok 56 /driver/enroll/update_nbis 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s ok 57 /driver/enroll/update_nbis_wrong_device 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s ok 58 /driver/enroll/update_nbis_wrong_driver 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s ok 59 /driver/enroll/update_nbis_missing_feature 311s # Start of error tests 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Device reported enroll completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s # libfprint-device-DEBUG: Device reported enroll completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s # libfprint-device-DEBUG: Device reported enroll completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s ok 60 /driver/enroll/error/no_print 311s # End of error tests 311s # End of enroll tests 311s # Start of verify tests 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 311s # 311s # libfprint-device-DEBUG: Device reported verify result 311s # libfprint-device-DEBUG: Device reported verify completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s ok 61 /driver/verify/fail 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 311s # 311s # libfprint-device-DEBUG: Device reported verify result 311s # libfprint-device-DEBUG: Device reported verify completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s ok 62 /driver/verify/retry 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 311s # 311s # libfprint-device-DEBUG: Device reported verify completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s ok 63 /driver/verify/error 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s ok 64 /driver/verify/not_supported 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Device reported verify result 311s # libfprint-device-DEBUG: Device reported verify completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s ok 65 /driver/verify/report_no_cb 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Device reported verify completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s ok 66 /driver/verify/not_reported 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Device reported verify result 311s # libfprint-device-DEBUG: Device reported verify completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s # libfprint-device-DEBUG: Device reported verify result 311s # libfprint-device-DEBUG: Device reported verify completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s # libfprint-device-DEBUG: Device reported verify result 311s # libfprint-device-DEBUG: Device reported verify completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s # libfprint-device-DEBUG: Device reported verify result 311s # libfprint-device-DEBUG: Device reported verify completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s # libfprint-device-DEBUG: Device reported verify result 311s # libfprint-device-DEBUG: Device reported verify completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s ok 67 /driver/verify/complete_retry 311s # End of verify tests 311s # Start of identify tests 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 311s # 311s # libfprint-device-DEBUG: Device reported identify result 311s # libfprint-device-DEBUG: Device reported identify completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s ok 68 /driver/identify/fail 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 311s # 311s # libfprint-device-DEBUG: Device reported identify result 311s # libfprint-device-DEBUG: Device reported identify completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s ok 69 /driver/identify/retry 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 311s # 311s # libfprint-device-DEBUG: Device reported identify completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s ok 70 /driver/identify/error 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Device reported identify completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s ok 71 /driver/identify/not_reported 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Device reported identify result 311s # libfprint-device-DEBUG: Device reported identify completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s # libfprint-device-DEBUG: Device reported identify result 311s # libfprint-device-DEBUG: Device reported identify completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s # libfprint-device-DEBUG: Device reported identify result 311s # libfprint-device-DEBUG: Device reported identify completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s ok 72 /driver/identify/complete_retry 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Device reported identify result 311s # libfprint-device-DEBUG: Device reported identify completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s ok 73 /driver/identify/report_no_cb 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 311s # 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 311s # 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 311s # 311s # libfprint-device-DEBUG: Device reported identify result 311s # libfprint-device-DEBUG: Device reported identify completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s ok 74 /driver/identify/suspend_continues 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 311s # 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 311s # 311s # libfprint-device-DEBUG: Device reported identify result 311s # libfprint-device-DEBUG: Device reported identify completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s ok 75 /driver/identify/suspend_succeeds 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 311s # 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 311s # 311s # libfprint-device-DEBUG: Device reported identify completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s ok 76 /driver/identify/suspend_busy_error 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 311s # 311s # libfprint-device-DEBUG: Device reported close completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s ok 77 /driver/identify/suspend_while_idle 311s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 311s # 311s # libfprint-device-DEBUG: Device reported open completion 311s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 311s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.30, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 313s Executing: libfprint-2/fpi-device.test 313s # libfprint-device-DEBUG: Updated temperature model after 2.00 seconds, ratio 0.30 -> 0.74, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_HOT 313s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 313s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 313s # 313s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 313s # 313s # libfprint-device-DEBUG: Device reported identify completion 313s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 313s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 313s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 1 -> 1, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 313s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 315s # libfprint-device-DEBUG: Updated temperature model after 2.09 seconds, ratio 0.74 -> 0.49, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_WARM 318s Executing: libfprint-2/fpi-device.test 318s # libfprint-device-DEBUG: Updated temperature model after 3.10 seconds, ratio 0.49 -> 0.26, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 318s # 318s # libfprint-device-DEBUG: Device reported close completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.26 -> 0.26, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s ok 78 /driver/identify/warmup_cooldown 318s # slow test /driver/identify/warmup_cooldown executed in 7.29 secs 318s # End of identify tests 318s # Start of capture tests 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 318s # 318s # libfprint-device-DEBUG: Device reported open completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 318s # 318s # libfprint-device-DEBUG: Device reported close completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s ok 79 /driver/capture/not_supported 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 318s # 318s # libfprint-device-DEBUG: Device reported open completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 318s # 318s # libfprint-device-DEBUG: Device reported capture completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 318s # 318s # libfprint-device-DEBUG: Device reported close completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 318s ok 80 /driver/capture/error 318s # End of capture tests 318s # Start of list tests 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 318s # 318s # libfprint-device-DEBUG: Device reported open completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 318s # 318s # libfprint-device-DEBUG: Device reported listing completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 318s # 318s # libfprint-device-DEBUG: Device reported close completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s ok 81 /driver/list/error 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 318s # 318s # libfprint-device-DEBUG: Device reported open completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 318s # 318s # libfprint-device-DEBUG: Device reported close completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s ok 82 /driver/list/no_storage 318s # End of list tests 318s # Start of delete tests 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 318s # 318s # libfprint-device-DEBUG: Device reported open completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 318s # 318s # libfprint-device-DEBUG: Device reported deletion completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 318s # 318s # libfprint-device-DEBUG: Device reported close completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s ok 83 /driver/delete/error 318s # End of delete tests 318s # Start of clear_storage tests 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 318s # 318s # libfprint-device-DEBUG: Device reported open completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 318s # 318s # libfprint-device-DEBUG: Device reported deletion completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 318s # 318s # libfprint-device-DEBUG: Device reported close completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s ok 84 /driver/clear_storage/error 318s # End of clear_storage tests 318s # Start of cancel tests 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 318s # 318s # libfprint-device-DEBUG: Device reported open completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 318s # 318s # libfprint-device-DEBUG: Device reported deletion completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 318s # 318s # libfprint-device-DEBUG: Device reported close completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s ok 85 /driver/cancel/fail 318s # End of cancel tests 318s # Start of get_current_action tests 318s # libfprint-device-DEBUG: Device reported open completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 318s # 318s # libfprint-device-DEBUG: Device reported close completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s ok 86 /driver/get_current_action/open 318s # End of get_current_action tests 318s # Start of get_cancellable tests 318s ok 87 /driver/get_cancellable/error 318s # libfprint-device-DEBUG: Device reported open completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 318s # 318s # libfprint-device-DEBUG: Device reported close completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s ok 88 /driver/get_cancellable/open 318s # Start of open tests 318s # libfprint-device-DEBUG: Device reported open completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 318s # 318s # libfprint-device-DEBUG: Device reported close completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s ok 89 /driver/get_cancellable/open/internal 318s # End of open tests 318s # End of get_cancellable tests 318s # Start of action_is_cancelled tests 318s # libfprint-device-DEBUG: Device reported open completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 318s # 318s # libfprint-device-DEBUG: Device reported close completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s ok 90 /driver/action_is_cancelled/open 318s ok 91 /driver/action_is_cancelled/error 318s # Start of open tests 318s # libfprint-device-DEBUG: Device reported open completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 318s # 318s # libfprint-device-DEBUG: Device reported close completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s ok 92 /driver/action_is_cancelled/open/internal 318s # End of open tests 318s # End of action_is_cancelled tests 318s # Start of complete_action tests 318s # Start of all tests 318s ok 93 /driver/complete_action/all/error 318s # End of all tests 318s # End of complete_action tests 318s # Start of action_error tests 318s ok 94 /driver/action_error/error 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 318s # 318s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN 318s # libfprint-device-DEBUG: Device reported open completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 318s # 318s # libfprint-device-DEBUG: Device reported open completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 318s # 318s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL 318s # libfprint-device-DEBUG: Device reported enroll completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 318s # 318s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY 318s # libfprint-device-DEBUG: Device reported verify completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 318s # 318s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 318s # libfprint-device-DEBUG: Device reported identify completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 318s # 318s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE 318s # libfprint-device-DEBUG: Device reported capture completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 318s # 318s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST 318s # libfprint-device-DEBUG: Device reported listing completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 318s # 318s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE 318s # libfprint-device-DEBUG: Device reported deletion completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 318s # 318s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLEAR_STORAGE 318s # libfprint-device-DEBUG: Device reported deletion completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 318s # 318s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE 318s # libfprint-device-DEBUG: Device reported close completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 318s ok 95 /driver/action_error/all 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 318s # 318s # libfprint-device-DEBUG: Device reported open completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 318s # 318s # libfprint-device-DEBUG: Device reported open completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 318s # 318s # libfprint-device-DEBUG: Device reported enroll completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 318s # 318s # libfprint-device-DEBUG: Device reported verify completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 318s # 318s # libfprint-device-DEBUG: Device reported identify completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 318s # 318s # libfprint-device-DEBUG: Device reported capture completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 318s # 318s # libfprint-device-DEBUG: Device reported listing completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 318s # 318s # libfprint-device-DEBUG: Device reported deletion completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 318s # 318s # libfprint-device-DEBUG: Device reported deletion completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 318s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 318s # 318s # libfprint-device-DEBUG: Device reported close completion 318s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 318s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 318s ok 96 /driver/action_error/fail 318s # End of action_error tests 318s # Start of timeout tests 318s ok 97 /driver/timeout/cancelled 318s # End of timeout tests 318s # End of driver tests 318s PASS: libfprint-2/fpi-device.test 318s Running test: libfprint-2/driver-egismoc-05a1.test 318s ** (umockdev-run:2348): DEBUG: 17:03:16.826: umockdev.vala:123: Created udev test bed /tmp/umockdev.ICZ6J2 318s ** (umockdev-run:2348): DEBUG: 17:03:16.826: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-5 318s ** (umockdev-run:2348): DEBUG: 17:03:16.828: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-5 (subsystem usb) 318s ** (umockdev-run:2348): DEBUG: 17:03:16.830: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.ICZ6J2/dev/bus/usb/001/003 318s ** (umockdev-run:2348): DEBUG: 17:03:16.830: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 318s ** (umockdev-run:2348): DEBUG: 17:03:16.831: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 318s ** (umockdev-run:2348): DEBUG: 17:03:16.833: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.ICZ6J2/dev/bus/usb/001/001 318s ** (umockdev-run:2348): DEBUG: 17:03:16.833: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 318s ** (umockdev-run:2348): DEBUG: 17:03:16.834: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 318s (process:2352): libfprint-context-DEBUG: 17:03:16.880: Initializing FpContext (libfprint version 1.94.7+tod1) 318s (process:2352): libfprint-tod-DEBUG: 17:03:16.880: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 318s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.882: 152867391: ../libfprint/drivers/egismoc/egismoc.c:1515 318s (process:2352): libfprint-context-DEBUG: 17:03:16.882: No driver found for USB device 1D6B:0002 318s (process:2352): libfprint-device-DEBUG: 17:03:16.882: Device reported probe completion 318s (process:2352): libfprint-device-DEBUG: 17:03:16.883: Completing action FPI_DEVICE_ACTION_PROBE in idle! 318s (process:2352): libfprint-device-DEBUG: 17:03:16.883: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 318s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.885: Opening device 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.886: [egismoc] DEV_INIT_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.886: [egismoc] DEV_INIT_STATES entering state 1 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.887: [egismoc] DEV_INIT_STATES entering state 2 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.887: [egismoc] DEV_INIT_STATES entering state 3 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.888: [egismoc] DEV_INIT_STATES entering state 4 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.888: [egismoc] DEV_INIT_STATES entering state 5 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.888: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.888: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.888: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.889: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.889: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.889: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.889: Firmware version callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.889: Response suffix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.889: Device firmware version is 9050.1.2.13 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.889: [egismoc] DEV_INIT_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.889: Task SSM done 319s (process:2352): libfprint-device-DEBUG: 17:03:16.889: Device reported open completion 319s (process:2352): libfprint-device-DEBUG: 17:03:16.889: Completing action FPI_DEVICE_ACTION_OPEN in idle! 319s (process:2352): libfprint-device-DEBUG: 17:03:16.889: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.890: List 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.890: [egismoc] LIST_STATES entering state 0 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.890: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.890: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.890: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.891: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.891: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.891: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.891: List callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.891: Device fingerprint 0: FP1-20231209-3-A9E16FBD-root 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.891: Device fingerprint 1: FP1-20231209-1-85DC4FAC-root 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.891: Device fingerprint 2: FP1-20231209-2-04EFB67C-root 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.891: Number of currently enrolled fingerprints on the device is 3 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.891: [egismoc] LIST_STATES entering state 1 319s (process:2352): libfprint-device-DEBUG: 17:03:16.892: Device reported listing completion 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.892: [egismoc] LIST_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.892: Task SSM done 319s (process:2352): libfprint-device-DEBUG: 17:03:16.892: Completing action FPI_DEVICE_ACTION_LIST in idle! 319s (process:2352): libfprint-device-DEBUG: 17:03:16.892: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.893: Clear storage 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.893: [egismoc] DELETE_STATES entering state 0 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.893: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.893: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.893: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.893: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.894: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.894: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.894: List callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.894: Device fingerprint 0: FP1-20231209-3-A9E16FBD-root 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.894: Device fingerprint 1: FP1-20231209-1-85DC4FAC-root 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.894: Device fingerprint 2: FP1-20231209-2-04EFB67C-root 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.894: Number of currently enrolled fingerprints on the device is 3 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.894: [egismoc] DELETE_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.894: Get delete command 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.894: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.894: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.894: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.894: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.895: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.895: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.895: Delete callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.895: Response prefix valid: yes 319s (process:2352): libfprint-device-DEBUG: 17:03:16.895: Device reported deletion completion 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.895: [egismoc] DELETE_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.895: Task SSM done 319s (process:2352): libfprint-device-DEBUG: 17:03:16.895: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 319s (process:2352): libfprint-device-DEBUG: 17:03:16.895: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.895: List 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.895: [egismoc] LIST_STATES entering state 0 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.895: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.895: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.895: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.895: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.896: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.896: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.896: List callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.896: Number of currently enrolled fingerprints on the device is 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.896: [egismoc] LIST_STATES entering state 1 319s (process:2352): libfprint-device-DEBUG: 17:03:16.896: Device reported listing completion 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.896: [egismoc] LIST_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.896: Task SSM done 319s (process:2352): libfprint-device-DEBUG: 17:03:16.896: Completing action FPI_DEVICE_ACTION_LIST in idle! 319s (process:2352): libfprint-device-DEBUG: 17:03:16.896: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 319s (process:2352): libfprint-device-DEBUG: 17:03:16.896: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.896: Enroll 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.896: [egismoc] ENROLL_STATES entering state 0 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.896: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.896: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.896: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.897: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.897: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.897: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.897: List callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.897: Number of currently enrolled fingerprints on the device is 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.897: [egismoc] ENROLL_STATES entering state 1 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.897: [egismoc] ENROLL_STATES entering state 2 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.897: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.897: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.897: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.897: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.898: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.898: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.898: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.898: [egismoc] ENROLL_STATES entering state 3 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.898: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.898: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.898: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.898: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.899: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.899: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.899: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.899: [egismoc] ENROLL_STATES entering state 4 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.899: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.899: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.899: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.899: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.899: [egismoc] ENROLL_STATES entering state 5 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.899: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.899: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.899: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.900: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.900: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.900: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.900: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.900: [egismoc] ENROLL_STATES entering state 6 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.900: Get check command 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.900: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.900: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.900: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.901: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.901: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.901: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.901: Enroll check callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.901: Response suffix valid: yes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.901: [egismoc] ENROLL_STATES entering state 7 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.901: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.901: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.901: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.902: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.902: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.902: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.902: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.902: [egismoc] ENROLL_STATES entering state 8 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.902: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.902: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.902: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.903: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.903: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.903: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.903: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.903: [egismoc] ENROLL_STATES entering state 9 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.903: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.903: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.903: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.903: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.904: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.904: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.904: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.904: [egismoc] ENROLL_STATES entering state 10 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.904: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.904: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.904: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.904: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.904: [egismoc] ENROLL_STATES entering state 11 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.904: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.904: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.904: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.905: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.905: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.905: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.905: Read capture callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.905: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.905: Response suffix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.905: Partial capture successful. Please touch the sensor again (1/10) 319s (process:2352): libfprint-device-DEBUG: 17:03:16.905: Device reported enroll progress, reported 1 of 10 have been completed 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.905: [egismoc] ENROLL_STATES entering state 8 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.905: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.905: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.905: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.906: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.906: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.906: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.906: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.906: [egismoc] ENROLL_STATES entering state 9 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.906: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.906: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.906: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.907: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.907: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.907: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.907: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.907: [egismoc] ENROLL_STATES entering state 10 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.907: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.907: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.908: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.908: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.908: [egismoc] ENROLL_STATES entering state 11 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.908: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.908: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.908: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.908: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.909: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.909: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.909: Read capture callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.909: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.909: Response suffix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.909: Partial capture successful. Please touch the sensor again (2/10) 319s (process:2352): libfprint-device-DEBUG: 17:03:16.909: Device reported enroll progress, reported 2 of 10 have been completed 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.909: [egismoc] ENROLL_STATES entering state 8 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.909: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.909: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.909: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.909: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.910: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.910: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.910: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.910: [egismoc] ENROLL_STATES entering state 9 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.910: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.910: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.910: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.910: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.911: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.911: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.911: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.911: [egismoc] ENROLL_STATES entering state 10 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.911: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.911: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.911: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.911: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.911: [egismoc] ENROLL_STATES entering state 11 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.911: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.911: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.911: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.911: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.912: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.912: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.912: Read capture callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.912: Response prefix valid: NO 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.912: Response prefix valid: NO 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.912: Response prefix valid: yes 319s (process:2352): libfprint-device-DEBUG: 17:03:16.912: Device reported enroll progress, reported 2 of 10 have been completed 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.912: [egismoc] ENROLL_STATES entering state 8 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.912: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.912: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.912: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.912: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.913: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.913: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.913: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.913: [egismoc] ENROLL_STATES entering state 9 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.913: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.913: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.913: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.913: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.914: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.914: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.914: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.914: [egismoc] ENROLL_STATES entering state 10 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.914: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.914: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.914: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.914: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.914: [egismoc] ENROLL_STATES entering state 11 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.914: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.914: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.914: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.915: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.915: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.915: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.915: Read capture callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.915: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.915: Response suffix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.915: Partial capture successful. Please touch the sensor again (3/10) 319s (process:2352): libfprint-device-DEBUG: 17:03:16.915: Device reported enroll progress, reported 3 of 10 have been completed 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.915: [egismoc] ENROLL_STATES entering state 8 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.915: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.915: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.915: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.916: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.916: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.916: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.916: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.916: [egismoc] ENROLL_STATES entering state 9 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.916: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.916: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.916: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.916: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.917: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.917: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.917: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.917: [egismoc] ENROLL_STATES entering state 10 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.917: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.917: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.917: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.917: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.917: [egismoc] ENROLL_STATES entering state 11 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.917: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.917: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.917: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.918: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.918: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.918: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.918: Read capture callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.918: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.918: Response suffix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.918: Partial capture successful. Please touch the sensor again (4/10) 319s (process:2352): libfprint-device-DEBUG: 17:03:16.918: Device reported enroll progress, reported 4 of 10 have been completed 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.918: [egismoc] ENROLL_STATES entering state 8 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.918: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.918: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.918: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.919: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.919: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.919: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.919: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.919: [egismoc] ENROLL_STATES entering state 9 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.919: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.919: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.919: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.920: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.920: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.920: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.920: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.920: [egismoc] ENROLL_STATES entering state 10 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.920: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.920: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.920: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.920: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.920: [egismoc] ENROLL_STATES entering state 11 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.920: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.920: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.920: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.921: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.921: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.921: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.921: Read capture callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.921: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.921: Response suffix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.921: Partial capture successful. Please touch the sensor again (5/10) 319s (process:2352): libfprint-device-DEBUG: 17:03:16.921: Device reported enroll progress, reported 5 of 10 have been completed 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.921: [egismoc] ENROLL_STATES entering state 8 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.921: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.921: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.921: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.922: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.922: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.922: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.922: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.922: [egismoc] ENROLL_STATES entering state 9 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.922: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.922: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.922: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.923: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.923: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.923: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.923: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.923: [egismoc] ENROLL_STATES entering state 10 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.923: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.923: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.924: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.924: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.924: [egismoc] ENROLL_STATES entering state 11 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.924: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.924: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.924: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.924: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.925: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.925: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.925: Read capture callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.925: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.925: Response suffix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.925: Partial capture successful. Please touch the sensor again (6/10) 319s (process:2352): libfprint-device-DEBUG: 17:03:16.925: Device reported enroll progress, reported 6 of 10 have been completed 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.925: [egismoc] ENROLL_STATES entering state 8 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.925: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.925: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.925: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.925: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.926: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.926: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.926: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.926: [egismoc] ENROLL_STATES entering state 9 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.926: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.926: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.926: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.926: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.926: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.926: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.926: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.926: [egismoc] ENROLL_STATES entering state 10 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.926: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.926: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.927: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.927: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.927: [egismoc] ENROLL_STATES entering state 11 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.927: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.927: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.927: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.927: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.928: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.928: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.928: Read capture callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.928: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.928: Response suffix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.928: Partial capture successful. Please touch the sensor again (7/10) 319s (process:2352): libfprint-device-DEBUG: 17:03:16.928: Device reported enroll progress, reported 7 of 10 have been completed 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.928: [egismoc] ENROLL_STATES entering state 8 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.928: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.928: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.928: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.928: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.929: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.929: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.929: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.929: [egismoc] ENROLL_STATES entering state 9 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.929: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.929: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.929: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.929: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.930: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.930: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.930: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.930: [egismoc] ENROLL_STATES entering state 10 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.930: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.930: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.930: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.930: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.930: [egismoc] ENROLL_STATES entering state 11 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.930: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.930: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.930: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.930: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.931: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.931: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.931: Read capture callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.931: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.931: Response suffix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.931: Partial capture successful. Please touch the sensor again (8/10) 319s (process:2352): libfprint-device-DEBUG: 17:03:16.931: Device reported enroll progress, reported 8 of 10 have been completed 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.931: [egismoc] ENROLL_STATES entering state 8 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.931: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.931: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.931: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.932: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.932: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.932: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.932: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.932: [egismoc] ENROLL_STATES entering state 9 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.932: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.932: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.932: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.932: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.933: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.933: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.933: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.933: [egismoc] ENROLL_STATES entering state 10 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.933: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.933: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.933: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.933: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.933: [egismoc] ENROLL_STATES entering state 11 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.933: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.933: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.933: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.934: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.934: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.934: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.934: Read capture callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.934: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.934: Response suffix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.934: Partial capture successful. Please touch the sensor again (9/10) 319s (process:2352): libfprint-device-DEBUG: 17:03:16.934: Device reported enroll progress, reported 9 of 10 have been completed 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.934: [egismoc] ENROLL_STATES entering state 8 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.934: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.934: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.934: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.935: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.935: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.935: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.935: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.935: [egismoc] ENROLL_STATES entering state 9 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.935: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.935: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.935: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.936: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.936: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.936: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.936: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.936: [egismoc] ENROLL_STATES entering state 10 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.936: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.936: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.937: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.937: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.937: [egismoc] ENROLL_STATES entering state 11 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.937: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.937: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.937: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.937: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.938: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.938: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.938: Read capture callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.938: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.938: Response suffix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.938: Partial capture successful. Please touch the sensor again (10/10) 319s (process:2352): libfprint-device-DEBUG: 17:03:16.938: Device reported enroll progress, reported 10 of 10 have been completed 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.938: [egismoc] ENROLL_STATES entering state 12 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.938: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.938: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.938: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.938: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.939: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.939: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.939: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.939: [egismoc] ENROLL_STATES entering state 13 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.939: New fingerprint ID: FP1-00000000-2-00000000-nobody 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.939: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.939: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.939: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.939: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.940: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.940: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.940: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.940: [egismoc] ENROLL_STATES entering state 14 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.940: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.940: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.940: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.940: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.940: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.940: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.940: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.940: [egismoc] ENROLL_STATES entering state 15 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.940: Enrollment was successful! 319s (process:2352): libfprint-device-DEBUG: 17:03:16.940: Device reported enroll completion 319s (process:2352): libfprint-device-DEBUG: 17:03:16.940: Device reported finger status change: FP_FINGER_STATUS_NONE 319s (process:2352): libfprint-device-DEBUG: 17:03:16.940: Print for finger FP_FINGER_LEFT_INDEX enrolled 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.940: [egismoc] ENROLL_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.940: Task SSM done 319s (process:2352): libfprint-device-DEBUG: 17:03:16.940: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 319s (process:2352): libfprint-device-DEBUG: 17:03:16.940: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.940: List 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.940: [egismoc] LIST_STATES entering state 0 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.940: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.940: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.940: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.941: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.941: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.941: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.941: List callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.941: Device fingerprint 0: FP1-00000000-2-00000000-nobody 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.941: Number of currently enrolled fingerprints on the device is 1 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.941: [egismoc] LIST_STATES entering state 1 319s (process:2352): libfprint-device-DEBUG: 17:03:16.941: Device reported listing completion 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.941: [egismoc] LIST_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.941: Task SSM done 319s (process:2352): libfprint-device-DEBUG: 17:03:16.941: Completing action FPI_DEVICE_ACTION_LIST in idle! 319s (process:2352): libfprint-device-DEBUG: 17:03:16.941: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 319s (process:2352): libfprint-device-DEBUG: 17:03:16.942: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.942: Identify or Verify 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.942: [egismoc] IDENTIFY_STATES entering state 0 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.942: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.942: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.942: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.942: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.943: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.943: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.943: List callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.943: Device fingerprint 0: FP1-00000000-2-00000000-nobody 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.943: Number of currently enrolled fingerprints on the device is 1 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.943: [egismoc] IDENTIFY_STATES entering state 1 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.943: [egismoc] IDENTIFY_STATES entering state 2 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.943: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.943: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.943: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.943: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.943: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.943: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.943: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.943: [egismoc] IDENTIFY_STATES entering state 3 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.943: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.943: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.943: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.944: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.944: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.944: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.944: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.944: [egismoc] IDENTIFY_STATES entering state 4 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.944: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.944: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.945: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.945: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.945: [egismoc] IDENTIFY_STATES entering state 5 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.945: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.945: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.945: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.945: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.946: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.946: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.946: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.946: [egismoc] IDENTIFY_STATES entering state 6 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.946: Get check command 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.946: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.946: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.946: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.946: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.947: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.947: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.947: Identify check callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.947: Response suffix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.947: Identify successful for: FP1-00000000-2-00000000-nobody 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.947: Verifying against: FP1-00000000-2-00000000-nobody 319s (process:2352): libfprint-device-DEBUG: 17:03:16.947: Device reported verify result 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.947: [egismoc] IDENTIFY_STATES entering state 7 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.947: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.947: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.947: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.947: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.947: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.948: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.948: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.948: [egismoc] IDENTIFY_STATES entering state 8 319s (process:2352): libfprint-device-DEBUG: 17:03:16.948: Device reported verify completion 319s (process:2352): libfprint-device-DEBUG: 17:03:16.948: Device reported finger status change: FP_FINGER_STATUS_NONE 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.948: [egismoc] IDENTIFY_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.948: Task SSM done 319s (process:2352): libfprint-device-DEBUG: 17:03:16.948: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 319s (process:2352): libfprint-device-DEBUG: 17:03:16.948: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 319s (process:2352): libfprint-device-DEBUG: 17:03:16.948: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.948: Identify or Verify 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.948: [egismoc] IDENTIFY_STATES entering state 0 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.948: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.948: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.948: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.949: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.949: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.949: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.949: List callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.949: Device fingerprint 0: FP1-00000000-2-00000000-nobody 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.949: Number of currently enrolled fingerprints on the device is 1 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.949: [egismoc] IDENTIFY_STATES entering state 1 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.949: [egismoc] IDENTIFY_STATES entering state 2 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.949: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.949: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.949: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.949: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.950: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.950: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.950: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.950: [egismoc] IDENTIFY_STATES entering state 3 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.950: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.950: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.950: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.950: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.951: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.951: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.951: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.951: [egismoc] IDENTIFY_STATES entering state 4 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.951: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.951: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.951: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.951: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.951: [egismoc] IDENTIFY_STATES entering state 5 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.951: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.951: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.951: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.952: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.952: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.952: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.952: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.952: [egismoc] IDENTIFY_STATES entering state 6 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.952: Get check command 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.952: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.952: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.952: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.953: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.953: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.953: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.953: Identify check callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.953: Response suffix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.953: Identify successful for: FP1-00000000-2-00000000-nobody 319s (process:2352): libfprint-device-DEBUG: 17:03:16.953: Device reported identify result 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.953: [egismoc] IDENTIFY_STATES entering state 7 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.953: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.953: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.953: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.954: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.954: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.954: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.954: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.954: [egismoc] IDENTIFY_STATES entering state 8 319s (process:2352): libfprint-device-DEBUG: 17:03:16.954: Device reported identify completion 319s (process:2352): libfprint-device-DEBUG: 17:03:16.954: Device reported finger status change: FP_FINGER_STATUS_NONE 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.954: [egismoc] IDENTIFY_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.954: Task SSM done 319s (process:2352): libfprint-device-DEBUG: 17:03:16.954: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 319s (process:2352): libfprint-device-DEBUG: 17:03:16.954: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 319s (process:2352): libfprint-device-DEBUG: 17:03:16.955: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.955: Enroll 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.955: [egismoc] ENROLL_STATES entering state 0 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.955: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.955: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.955: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.955: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.955: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.955: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.955: List callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.955: Device fingerprint 0: FP1-00000000-2-00000000-nobody 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.955: Number of currently enrolled fingerprints on the device is 1 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.955: [egismoc] ENROLL_STATES entering state 1 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.955: [egismoc] ENROLL_STATES entering state 2 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.955: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.955: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.955: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.956: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.956: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.956: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.956: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.956: [egismoc] ENROLL_STATES entering state 3 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.956: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.956: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.956: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.957: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.957: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.957: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.957: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.957: [egismoc] ENROLL_STATES entering state 4 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.957: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.957: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.958: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.958: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.958: [egismoc] ENROLL_STATES entering state 5 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.958: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.958: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.958: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.958: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.959: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.959: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.959: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.959: [egismoc] ENROLL_STATES entering state 6 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.959: Get check command 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.959: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.959: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.959: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.959: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.959: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.959: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.959: Enroll check callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.959: Response suffix valid: NO 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.959: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.959: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.959: Task SSM done 319s (process:2352): libfprint-device-DEBUG: 17:03:16.959: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 319s (process:2352): libfprint-device-DEBUG: 17:03:16.959: Device reported enroll completion 319s (process:2352): libfprint-device-DEBUG: 17:03:16.959: Device reported finger status change: FP_FINGER_STATUS_NONE 319s (process:2352): libfprint-device-DEBUG: 17:03:16.959: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 319s (process:2352): libfprint-device-DEBUG: 17:03:16.959: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.960: List 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.960: [egismoc] LIST_STATES entering state 0 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.960: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.960: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.960: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.960: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.961: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.961: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.961: List callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.961: Device fingerprint 0: FP1-00000000-2-00000000-nobody 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.961: Number of currently enrolled fingerprints on the device is 1 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.961: [egismoc] LIST_STATES entering state 1 319s (process:2352): libfprint-device-DEBUG: 17:03:16.961: Device reported listing completion 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.961: [egismoc] LIST_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.961: Task SSM done 319s (process:2352): libfprint-device-DEBUG: 17:03:16.961: Completing action FPI_DEVICE_ACTION_LIST in idle! 319s (process:2352): libfprint-device-DEBUG: 17:03:16.961: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 319s (process:2352): libfprint-device-DEBUG: 17:03:16.961: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.961: Enroll 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.961: [egismoc] ENROLL_STATES entering state 0 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.961: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.961: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.961: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.961: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.962: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.962: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.962: List callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.962: Device fingerprint 0: FP1-00000000-2-00000000-nobody 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.962: Number of currently enrolled fingerprints on the device is 1 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.962: [egismoc] ENROLL_STATES entering state 1 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.962: [egismoc] ENROLL_STATES entering state 2 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.962: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.962: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.962: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.962: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.962: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.962: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.962: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.962: [egismoc] ENROLL_STATES entering state 3 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.962: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.962: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.962: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.963: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.963: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.963: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.963: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.963: [egismoc] ENROLL_STATES entering state 4 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.963: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.963: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.964: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.964: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.964: [egismoc] ENROLL_STATES entering state 5 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.964: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.964: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.964: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.964: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.965: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.965: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.965: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.965: [egismoc] ENROLL_STATES entering state 6 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.965: Get check command 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.965: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.965: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.965: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.965: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.966: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.966: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.966: Enroll check callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.966: Response suffix valid: yes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.966: [egismoc] ENROLL_STATES entering state 7 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.966: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.966: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.966: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.966: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.966: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.966: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.966: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.966: [egismoc] ENROLL_STATES entering state 8 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.966: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.966: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.966: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.967: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.967: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.967: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.967: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.967: [egismoc] ENROLL_STATES entering state 9 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.967: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.967: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.967: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.968: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.968: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.968: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.968: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.968: [egismoc] ENROLL_STATES entering state 10 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.968: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.968: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.969: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.969: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.969: [egismoc] ENROLL_STATES entering state 11 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.969: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.969: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.969: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.969: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.970: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.970: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.970: Read capture callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.970: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.970: Response suffix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.970: Partial capture successful. Please touch the sensor again (1/10) 319s (process:2352): libfprint-device-DEBUG: 17:03:16.970: Device reported enroll progress, reported 1 of 10 have been completed 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.970: [egismoc] ENROLL_STATES entering state 8 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.970: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.970: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.970: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.970: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.971: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.971: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.971: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.971: [egismoc] ENROLL_STATES entering state 9 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.971: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.971: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.971: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.971: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.972: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.972: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.972: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.972: [egismoc] ENROLL_STATES entering state 10 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.972: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.972: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.972: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.972: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.972: [egismoc] ENROLL_STATES entering state 11 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.972: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.972: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.972: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.972: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.973: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.973: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.973: Read capture callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.973: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.973: Response suffix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.973: Partial capture successful. Please touch the sensor again (2/10) 319s (process:2352): libfprint-device-DEBUG: 17:03:16.973: Device reported enroll progress, reported 2 of 10 have been completed 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.973: [egismoc] ENROLL_STATES entering state 8 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.973: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.973: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.973: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.973: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.974: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.974: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.974: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.974: [egismoc] ENROLL_STATES entering state 9 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.974: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.974: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.974: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.974: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.975: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.975: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.975: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.975: [egismoc] ENROLL_STATES entering state 10 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.975: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.975: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.975: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.975: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.975: [egismoc] ENROLL_STATES entering state 11 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.975: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.975: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.975: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.976: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.976: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.976: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.976: Read capture callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.976: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.976: Response suffix valid: NO 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.976: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.976: Response suffix valid: yes 319s (process:2352): libfprint-device-DEBUG: 17:03:16.976: Device reported enroll progress, reported 2 of 10 have been completed 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.976: [egismoc] ENROLL_STATES entering state 8 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.976: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.976: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.976: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.977: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.977: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.977: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.977: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.977: [egismoc] ENROLL_STATES entering state 9 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.977: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.977: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.977: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.978: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.978: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.978: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.978: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.978: [egismoc] ENROLL_STATES entering state 10 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.978: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.978: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.979: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.979: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.979: [egismoc] ENROLL_STATES entering state 11 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.979: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.979: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.979: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.979: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.979: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.979: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.979: Read capture callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.979: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.979: Response suffix valid: NO 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.979: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.979: Response suffix valid: yes 319s (process:2352): libfprint-device-DEBUG: 17:03:16.979: Device reported enroll progress, reported 2 of 10 have been completed 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.979: [egismoc] ENROLL_STATES entering state 8 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.979: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.979: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.979: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.980: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.980: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.980: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.980: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.980: [egismoc] ENROLL_STATES entering state 9 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.980: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.980: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.980: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.981: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.981: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.981: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.981: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.981: [egismoc] ENROLL_STATES entering state 10 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.981: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.981: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.982: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.982: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.982: [egismoc] ENROLL_STATES entering state 11 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.982: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.982: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.982: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.982: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.983: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.983: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.983: Read capture callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.983: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.983: Response suffix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.983: Partial capture successful. Please touch the sensor again (3/10) 319s (process:2352): libfprint-device-DEBUG: 17:03:16.983: Device reported enroll progress, reported 3 of 10 have been completed 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.983: [egismoc] ENROLL_STATES entering state 8 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.983: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.983: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.983: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.983: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.984: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.984: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.984: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.984: [egismoc] ENROLL_STATES entering state 9 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.984: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.984: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.984: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.984: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.984: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.984: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.984: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.985: [egismoc] ENROLL_STATES entering state 10 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.985: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.985: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.985: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.985: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.985: [egismoc] ENROLL_STATES entering state 11 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.985: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.985: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.985: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.985: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.986: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.986: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.986: Read capture callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.986: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.986: Response suffix valid: NO 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.986: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.986: Response suffix valid: yes 319s (process:2352): libfprint-device-DEBUG: 17:03:16.986: Device reported enroll progress, reported 3 of 10 have been completed 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.986: [egismoc] ENROLL_STATES entering state 8 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.986: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.986: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.986: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.986: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.987: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.987: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.987: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.987: [egismoc] ENROLL_STATES entering state 9 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.987: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.987: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.987: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.987: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.988: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.988: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.988: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.988: [egismoc] ENROLL_STATES entering state 10 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.988: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.988: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.988: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.988: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.988: [egismoc] ENROLL_STATES entering state 11 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.988: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.988: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.988: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.989: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.989: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.989: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.989: Read capture callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.989: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.989: Response suffix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.989: Partial capture successful. Please touch the sensor again (4/10) 319s (process:2352): libfprint-device-DEBUG: 17:03:16.989: Device reported enroll progress, reported 4 of 10 have been completed 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.989: [egismoc] ENROLL_STATES entering state 8 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.989: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.989: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.989: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.990: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.990: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.990: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.990: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.990: [egismoc] ENROLL_STATES entering state 9 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.990: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.990: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.990: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.990: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.991: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.991: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.991: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.991: [egismoc] ENROLL_STATES entering state 10 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.991: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.991: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.991: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.991: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.991: [egismoc] ENROLL_STATES entering state 11 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.991: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.991: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.991: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.992: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.992: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.992: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.992: Read capture callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.992: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.992: Response suffix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.992: Partial capture successful. Please touch the sensor again (5/10) 319s (process:2352): libfprint-device-DEBUG: 17:03:16.992: Device reported enroll progress, reported 5 of 10 have been completed 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.992: [egismoc] ENROLL_STATES entering state 8 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.992: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.992: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.992: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.993: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.993: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.993: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.993: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.993: [egismoc] ENROLL_STATES entering state 9 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.993: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.993: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.993: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.994: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.994: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.994: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.994: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.994: [egismoc] ENROLL_STATES entering state 10 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.994: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.994: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.995: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.995: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.995: [egismoc] ENROLL_STATES entering state 11 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.995: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.995: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.995: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.995: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.996: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.996: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.996: Read capture callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.996: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.996: Response suffix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.996: Partial capture successful. Please touch the sensor again (6/10) 319s (process:2352): libfprint-device-DEBUG: 17:03:16.996: Device reported enroll progress, reported 6 of 10 have been completed 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.996: [egismoc] ENROLL_STATES entering state 8 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.996: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.996: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.996: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.996: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.996: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.996: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.996: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.996: [egismoc] ENROLL_STATES entering state 9 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.996: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.996: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.996: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.997: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.997: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.997: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.997: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.997: [egismoc] ENROLL_STATES entering state 10 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.997: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:16.997: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.998: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:16.998: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.998: [egismoc] ENROLL_STATES entering state 11 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.998: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.998: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.998: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.998: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.998: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.999: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.999: Read capture callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.999: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.999: Response suffix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.999: Partial capture successful. Please touch the sensor again (7/10) 319s (process:2352): libfprint-device-DEBUG: 17:03:16.999: Device reported enroll progress, reported 7 of 10 have been completed 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.999: [egismoc] ENROLL_STATES entering state 8 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.999: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.999: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.999: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:16.999: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:16.999: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.000: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.000: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.000: [egismoc] ENROLL_STATES entering state 9 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.000: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.000: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.000: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.000: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.000: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.000: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.000: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.000: [egismoc] ENROLL_STATES entering state 10 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.000: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:17.000: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.001: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:17.001: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.001: [egismoc] ENROLL_STATES entering state 11 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.001: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.001: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.001: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.001: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.002: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.002: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.002: Read capture callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.002: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.002: Response suffix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.002: Partial capture successful. Please touch the sensor again (8/10) 319s (process:2352): libfprint-device-DEBUG: 17:03:17.002: Device reported enroll progress, reported 8 of 10 have been completed 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.002: [egismoc] ENROLL_STATES entering state 8 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.002: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.002: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.002: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.002: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.003: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.003: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.003: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.003: [egismoc] ENROLL_STATES entering state 9 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.003: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.003: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.003: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.003: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.004: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.004: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.004: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.004: [egismoc] ENROLL_STATES entering state 10 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.004: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:17.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.004: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:17.004: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.004: [egismoc] ENROLL_STATES entering state 11 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.004: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.004: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.004: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.004: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.005: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.005: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.005: Read capture callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.005: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.005: Response suffix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.005: Partial capture successful. Please touch the sensor again (9/10) 319s (process:2352): libfprint-device-DEBUG: 17:03:17.005: Device reported enroll progress, reported 9 of 10 have been completed 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.005: [egismoc] ENROLL_STATES entering state 8 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.005: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.005: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.005: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.005: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.006: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.006: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.006: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.006: [egismoc] ENROLL_STATES entering state 9 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.006: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.006: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.006: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.006: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.007: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.007: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.007: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.007: [egismoc] ENROLL_STATES entering state 10 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.007: Wait for finger on sensor 319s (process:2352): libfprint-device-DEBUG: 17:03:17.007: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.007: Finger on sensor callback 319s (process:2352): libfprint-device-DEBUG: 17:03:17.007: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.007: [egismoc] ENROLL_STATES entering state 11 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.007: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.007: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.007: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.008: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.008: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.008: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.008: Read capture callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.008: Response prefix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.008: Response suffix valid: yes 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.008: Partial capture successful. Please touch the sensor again (10/10) 319s (process:2352): libfprint-device-DEBUG: 17:03:17.008: Device reported enroll progress, reported 10 of 10 have been completed 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.008: [egismoc] ENROLL_STATES entering state 12 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.008: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.008: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.008: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.009: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.009: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.009: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.009: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.009: [egismoc] ENROLL_STATES entering state 13 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.009: New fingerprint ID: FP1-00000000-7-00000000-nobody 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.009: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.009: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.009: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.010: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.010: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.010: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.010: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.010: [egismoc] ENROLL_STATES entering state 14 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.010: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.010: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.010: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.010: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.011: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.011: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.011: Task SSM next state callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.011: [egismoc] ENROLL_STATES entering state 15 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.011: Enrollment was successful! 319s (process:2352): libfprint-device-DEBUG: 17:03:17.011: Device reported enroll completion 319s (process:2352): libfprint-device-DEBUG: 17:03:17.011: Device reported finger status change: FP_FINGER_STATUS_NONE 319s (process:2352): libfprint-device-DEBUG: 17:03:17.011: Print for finger FP_FINGER_RIGHT_INDEX enrolled 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.011: [egismoc] ENROLL_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.011: Task SSM done 319s (process:2352): libfprint-device-DEBUG: 17:03:17.011: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 319s (process:2352): libfprint-device-DEBUG: 17:03:17.011: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.011: List 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.011: [egismoc] LIST_STATES entering state 0 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.011: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.011: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.011: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.011: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.012: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.012: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.012: List callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.012: Device fingerprint 0: FP1-00000000-2-00000000-nobody 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.012: Device fingerprint 1: FP1-00000000-7-00000000-nobody 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.012: Number of currently enrolled fingerprints on the device is 2 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.012: [egismoc] LIST_STATES entering state 1 319s (process:2352): libfprint-device-DEBUG: 17:03:17.012: Device reported listing completion 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.012: [egismoc] LIST_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.012: Task SSM done 319s (process:2352): libfprint-device-DEBUG: 17:03:17.012: Completing action FPI_DEVICE_ACTION_LIST in idle! 319s (process:2352): libfprint-device-DEBUG: 17:03:17.012: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.012: Delete 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.012: [egismoc] DELETE_STATES entering state 0 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.012: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.012: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.012: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.013: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.013: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.013: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.013: List callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.013: Device fingerprint 0: FP1-00000000-2-00000000-nobody 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.013: Device fingerprint 1: FP1-00000000-7-00000000-nobody 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.013: Number of currently enrolled fingerprints on the device is 2 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.013: [egismoc] DELETE_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.013: Get delete command 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.013: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.013: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.013: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.013: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.014: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.014: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.014: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.014: Delete callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.014: Response prefix valid: yes 319s (process:2352): libfprint-device-DEBUG: 17:03:17.014: Device reported deletion completion 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.014: [egismoc] DELETE_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.014: Task SSM done 319s (process:2352): libfprint-device-DEBUG: 17:03:17.014: Completing action FPI_DEVICE_ACTION_DELETE in idle! 319s (process:2352): libfprint-device-DEBUG: 17:03:17.014: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.014: List 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.014: [egismoc] LIST_STATES entering state 0 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.014: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.014: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.014: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.014: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.015: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.015: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.015: List callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.015: Device fingerprint 0: FP1-00000000-7-00000000-nobody 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.015: Number of currently enrolled fingerprints on the device is 1 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.015: [egismoc] LIST_STATES entering state 1 319s (process:2352): libfprint-device-DEBUG: 17:03:17.015: Device reported listing completion 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.015: [egismoc] LIST_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.015: Task SSM done 319s (process:2352): libfprint-device-DEBUG: 17:03:17.015: Completing action FPI_DEVICE_ACTION_LIST in idle! 319s (process:2352): libfprint-device-DEBUG: 17:03:17.015: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.015: Clear storage 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.015: [egismoc] DELETE_STATES entering state 0 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.015: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.015: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.015: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.016: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.016: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.016: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.016: List callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.016: Device fingerprint 0: FP1-00000000-7-00000000-nobody 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.016: Number of currently enrolled fingerprints on the device is 1 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.016: [egismoc] DELETE_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.016: Get delete command 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.016: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.016: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.016: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.016: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.017: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.017: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.017: Delete callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.017: Response prefix valid: yes 319s (process:2352): libfprint-device-DEBUG: 17:03:17.017: Device reported deletion completion 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.017: [egismoc] DELETE_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.017: Task SSM done 319s (process:2352): libfprint-device-DEBUG: 17:03:17.017: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 319s (process:2352): libfprint-device-DEBUG: 17:03:17.017: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.017: List 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.017: [egismoc] LIST_STATES entering state 0 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.017: Execute command and get response 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.017: Get check bytes 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.017: [egismoc] CMD_STATES entering state 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.017: [egismoc] CMD_STATES entering state 1 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.018: Command receive callback 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.018: [egismoc] CMD_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.018: List callback 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.018: Number of currently enrolled fingerprints on the device is 0 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.018: [egismoc] LIST_STATES entering state 1 319s (process:2352): libfprint-device-DEBUG: 17:03:17.018: Device reported listing completion 319s (process:2352): libfprint-SSM-DEBUG: 17:03:17.018: [egismoc] LIST_STATES completed successfully 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.018: Task SSM done 319s (process:2352): libfprint-device-DEBUG: 17:03:17.018: Completing action FPI_DEVICE_ACTION_LIST in idle! 319s (process:2352): libfprint-device-DEBUG: 17:03:17.018: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.018: Closing device 319s (process:2352): libfprint-egismoc-DEBUG: 17:03:17.018: Cancel 319s (process:2352): libfprint-device-DEBUG: 17:03:17.018: Device reported close completion 319s (process:2352): libfprint-device-DEBUG: 17:03:17.018: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 319s (process:2352): libfprint-device-DEBUG: 17:03:17.018: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 319s listing - device should have prints 319s clear device storage 319s clear done 319s listing - device should be empty 319s enrolling 319s finger status: 319s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf435ebd1df00 (FpiDeviceEgisMoc at 0xe481340)>, 1, , None, None) 319s finger status: 319s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf435ebd1df00 (FpiDeviceEgisMoc at 0xe481340)>, 2, , None, None) 319s finger status: 319s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf435ebd1df00 (FpiDeviceEgisMoc at 0xe481340)>, 2, None, None, GLib.Error('Your device is having trouble recognizing you. Make sure your sensor is clean.', 'fp - device - retry - quark', 3)) 319s finger status: 319s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf435ebd1df00 (FpiDeviceEgisMoc at 0xe481340)>, 3, , None, None) 319s finger status: 319s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf435ebd1df00 (FpiDeviceEgisMoc at 0xe481340)>, 4, , None, None) 319s finger status: 319s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf435ebd1df00 (FpiDeviceEgisMoc at 0xe481340)>, 5, , None, None) 319s finger status: 319s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf435ebd1df00 (FpiDeviceEgisMoc at 0xe481340)>, 6, , None, None) 319s finger status: 319s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf435ebd1df00 (FpiDeviceEgisMoc at 0xe481340)>, 7, , None, None) 319s finger status: 319s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf435ebd1df00 (FpiDeviceEgisMoc at 0xe481340)>, 8, , None, None) 319s finger status: 319s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf435ebd1df00 (FpiDeviceEgisMoc at 0xe481340)>, 9, , None, None) 319s finger status: 319s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf435ebd1df00 (FpiDeviceEgisMoc at 0xe481340)>, 10, , None, None) 319s enroll done 319s listing - device should have 1 print 319s verifying 319s verify done 319s async identifying 319s indentification_done: 319s try to enroll duplicate 319s duplicate enroll attempt done 319s listing - device should still only have 1 print 319s enroll new finger 319s finger status: 319s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf435ebd1df00 (FpiDeviceEgisMoc at 0xe481340)>, 1, , None, None) 319s finger status: 319s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf435ebd1df00 (FpiDeviceEgisMoc at 0xe481340)>, 2, , None, None) 319s finger status: 319s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf435ebd1df00 (FpiDeviceEgisMoc at 0xe481340)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 319s finger status: 319s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf435ebd1df00 (FpiDeviceEgisMoc at 0xe481340)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 319s finger status: 319s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf435ebd1df00 (FpiDeviceEgisMoc at 0xe481340)>, 3, , None, None) 319s finger status: 319s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf435ebd1df00 (FpiDeviceEgisMoc at 0xe481340)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 319s finger status: 319s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf435ebd1df00 (FpiDeviceEgisMoc at 0xe481340)>, 4, , None, None) 319s finger status: 319s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf435ebd1df00 (FpiDeviceEgisMoc at 0xe481340)>, 5, , None, None) 319s finger status: 319s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf435ebd1df00 (FpiDeviceEgisMoc at 0xe481340)>, 6, , None, None) 319s finger status: 319s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf435ebd1df00 (FpiDeviceEgisMoc at 0xe481340)>, 7, , None, None) 319s finger status: 319s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf435ebd1df00 (FpiDeviceEgisMoc at 0xe481340)>, 8, , None, None) 319s finger status: 319s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf435ebd1df00 (FpiDeviceEgisMoc at 0xe481340)>, 9, , None, None) 319s finger status: 319s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf435ebd1df00 (FpiDeviceEgisMoc at 0xe481340)>, 10, , None, None) 319s enroll new finger done 319s listing - device should have 2 prints 319s deleting first print 319s delete done 319s listing - device should only have second print 319s clear device storage 319s clear done 319s listing - device should be empty 319s ** (umockdev-run:2348): DEBUG: 17:03:17.029: umockdev.vala:150: Removing test bed /tmp/umockdev.ICZ6J2 319s (umockdev-run:2348): GLib-DEBUG: 17:03:17.033: unsetenv() is not thread-safe and should not be used after threads are created 319s PASS: libfprint-2/driver-egismoc-05a1.test 319s Running test: libfprint-2/driver-vfs301.test 319s ** (umockdev-run:2360): DEBUG: 17:03:17.075: umockdev.vala:123: Created udev test bed /tmp/umockdev.55HAK2 319s ** (umockdev-run:2360): DEBUG: 17:03:17.075: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3 319s ** (umockdev-run:2360): DEBUG: 17:03:17.077: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3 (subsystem usb) 319s ** (umockdev-run:2360): DEBUG: 17:03:17.079: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.55HAK2/dev/bus/usb/002/005 319s ** (umockdev-run:2360): DEBUG: 17:03:17.079: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2/2-1 319s ** (umockdev-run:2360): DEBUG: 17:03:17.080: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1d.0/usb2/2-1 (subsystem usb) 319s ** (umockdev-run:2360): DEBUG: 17:03:17.081: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.55HAK2/dev/bus/usb/002/002 319s ** (umockdev-run:2360): DEBUG: 17:03:17.081: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2 319s ** (umockdev-run:2360): DEBUG: 17:03:17.082: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1d.0/usb2 (subsystem usb) 319s ** (umockdev-run:2360): DEBUG: 17:03:17.084: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.55HAK2/dev/bus/usb/002/001 319s ** (umockdev-run:2360): DEBUG: 17:03:17.084: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:1d.0 319s ** (umockdev-run:2360): DEBUG: 17:03:17.084: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:1d.0 (subsystem pci) 319s (umockdev-run:2360): GLib-GIO-DEBUG: 17:03:17.086: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 319s (process:2364): libfprint-context-DEBUG: 17:03:17.148: Initializing FpContext (libfprint version 1.94.7+tod1) 319s (process:2364): libfprint-tod-DEBUG: 17:03:17.148: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 319s (process:2364): libfprint-context-DEBUG: 17:03:17.150: No driver found for USB device 8087:0020 319s (process:2364): libfprint-context-DEBUG: 17:03:17.150: No driver found for USB device 1D6B:0002 319s (process:2364): libfprint-device-DEBUG: 17:03:17.151: Device reported probe completion 319s (process:2364): libfprint-device-DEBUG: 17:03:17.151: Completing action FPI_DEVICE_ACTION_PROBE in idle! 319s (process:2364): libfprint-device-DEBUG: 17:03:17.151: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s libusb: error [op_handle_events] cannot find handle for fd 9 319s (process:2364): libfprint-image_device-DEBUG: 17:03:17.154: Image device open completed 319s (process:2364): libfprint-device-DEBUG: 17:03:17.154: Device reported open completion 319s (process:2364): libfprint-device-DEBUG: 17:03:17.154: Completing action FPI_DEVICE_ACTION_OPEN in idle! 319s (process:2364): libfprint-device-DEBUG: 17:03:17.154: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 319s (process:2364): libfprint-device-DEBUG: 17:03:17.154: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 319s (process:2364): libfprint-image_device-DEBUG: 17:03:17.154: Activating image device 319s (process:2364): libfprint-image_device-DEBUG: 17:03:17.154: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 319s (process:2364): libfprint-SSM-DEBUG: 17:03:17.154: [vfs301] 1 entering state 0 319s (process:2364): libfprint-SSM-DEBUG: 17:03:17.181: [vfs301] 1 completed successfully 319s (process:2364): libfprint-image_device-DEBUG: 17:03:17.181: Image device activation completed 319s (process:2364): libfprint-image_device-DEBUG: 17:03:17.181: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 319s (process:2364): libfprint-image_device-DEBUG: 17:03:17.181: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 319s (process:2364): libfprint-SSM-DEBUG: 17:03:17.181: [vfs301] M_LOOP_NUM_STATES entering state 0 319s (process:2364): libfprint-SSM-DEBUG: 17:03:17.181: [vfs301] M_LOOP_NUM_STATES entering state 1 319s (process:2364): libfprint-device-DEBUG: 17:03:17.182: Device reported finger status change: FP_FINGER_STATUS_NEEDED 319s (process:2364): libfprint-device-DEBUG: 17:03:17.255: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 319s (process:2364): libfprint-SSM-DEBUG: 17:03:17.382: [vfs301] M_LOOP_NUM_STATES entering state 2 319s (process:2364): libfprint-SSM-DEBUG: 17:03:17.383: [vfs301] M_LOOP_NUM_STATES entering state 1 319s (process:2364): libfprint-SSM-DEBUG: 17:03:17.583: [vfs301] M_LOOP_NUM_STATES entering state 2 319s (process:2364): libfprint-SSM-DEBUG: 17:03:17.584: [vfs301] M_LOOP_NUM_STATES entering state 3 319s (process:2364): libfprint-device-DEBUG: 17:03:17.584: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 319s (process:2364): libfprint-image_device-DEBUG: 17:03:17.584: Image device reported finger status: on 319s (process:2364): libfprint-image_device-DEBUG: 17:03:17.584: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 319s (process:2364): libfprint-SSM-DEBUG: 17:03:17.585: [vfs301] M_LOOP_NUM_STATES entering state 4 319s (process:2364): libfprint-SSM-DEBUG: 17:03:17.785: [vfs301] M_LOOP_NUM_STATES entering state 5 319s (process:2364): libfprint-SSM-DEBUG: 17:03:17.787: [vfs301] M_LOOP_NUM_STATES entering state 6 319s (process:2364): libfprint-image_device-DEBUG: 17:03:17.787: Image device captured an image 319s (process:2364): libfprint-image_device-DEBUG: 17:03:17.791: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 319s (process:2364): libfprint-device-DEBUG: 17:03:17.791: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2364): libfprint-SSM-DEBUG: 17:03:17.791: [vfs301] M_LOOP_NUM_STATES completed successfully 319s (process:2364): libfprint-device-DEBUG: 17:03:17.791: Device reported finger status change: FP_FINGER_STATUS_NONE 319s (process:2364): libfprint-image_device-DEBUG: 17:03:17.791: Image device reported finger status: off 319s (process:2364): libfprint-image_device-DEBUG: 17:03:17.791: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 319s (process:2364): libfprint-image_device-DEBUG: 17:03:17.791: Deactivating image device 319s (process:2364): libfprint-image_device-DEBUG: 17:03:17.791: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 319s (process:2364): libfprint-image_device-DEBUG: 17:03:17.791: Image device deactivation completed 319s (process:2364): libfprint-image_device-DEBUG: 17:03:17.791: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 319s (process:2364): libfprint-image-DEBUG: 17:03:17.821: Minutiae scan completed in 0.033383 secs 319s (process:2364): libfprint-device-DEBUG: 17:03:17.822: Device reported capture completion 319s (process:2364): libfprint-device-DEBUG: 17:03:17.822: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 319s (process:2364): libfprint-device-DEBUG: 17:03:17.822: Updated temperature model after 0.57 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 319s (process:2364): libfprint-image_device-DEBUG: 17:03:17.822: Image device close completed 319s (process:2364): libfprint-device-DEBUG: 17:03:17.822: Device reported close completion 319s (process:2364): libfprint-device-DEBUG: 17:03:17.822: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 319s (process:2364): libfprint-device-DEBUG: 17:03:17.822: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 319s ** (umockdev-run:2360): DEBUG: 17:03:17.883: umockdev.vala:150: Removing test bed /tmp/umockdev.55HAK2 319s (umockdev-run:2360): GLib-DEBUG: 17:03:17.888: unsetenv() is not thread-safe and should not be used after threads are created 319s Comparing PNGs /tmp/libfprint-umockdev-test-vpzp3n6u/capture.png and /usr/share/installed-tests/libfprint-2/vfs301/capture.png 319s PASS: libfprint-2/driver-vfs301.test 319s Running test: libfprint-2/fpi-ssm.test 319s TAP version 13 319s # random seed: R02S09421e7d2515df4db575ed192baeba3a 319s 1..42 319s # Start of ssm tests 319s ok 1 /ssm/new 319s ok 2 /ssm/set_data 319s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 319s ok 3 /ssm/start 319s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 319s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 319s ok 4 /ssm/next 319s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 319s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 319s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 319s ok 5 /ssm/jump_to_state 319s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 319s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 319s ok 6 /ssm/mark_completed 319s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 319s # 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. 319s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 319s ok 7 /ssm/mark_failed 319s # Start of new tests 319s ok 8 /ssm/new/full 319s ok 9 /ssm/new/no_handler 319s ok 10 /ssm/new/wrong_states 319s # End of new tests 319s # Start of set_data tests 319s ok 11 /ssm/set_data/cleanup 319s # End of set_data tests 319s # Start of start tests 319s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE entering state 0 319s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE completed successfully 319s ok 12 /ssm/start/single 319s # End of start tests 319s # Start of next tests 319s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 319s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 319s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 319s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 319s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 319s ok 13 /ssm/next/complete 319s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 319s ok 14 /ssm/next/not_started 319s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 319s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 320s ok 15 /ssm/next/with_delayed 320s # End of next tests 320s # Start of jump_to_state tests 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 320s ok 16 /ssm/jump_to_state/not_started 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 320s ok 17 /ssm/jump_to_state/with_delayed 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 320s ok 18 /ssm/jump_to_state/last 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 14 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state -10 320s ok 19 /ssm/jump_to_state/wrong 320s # End of jump_to_state tests 320s # Start of mark_completed tests 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 320s ok 20 /ssm/mark_completed/not_started 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 320s ok 21 /ssm/mark_completed/with_delayed 320s # End of mark_completed tests 320s # Start of mark_failed tests 320s # 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. 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 320s ok 22 /ssm/mark_failed/not_started 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 320s # 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. 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 320s ok 23 /ssm/mark_failed/with_delayed 320s # End of mark_failed tests 320s # Start of delayed tests 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 320s ok 24 /ssm/delayed/next 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 320s ok 25 /ssm/delayed/jump_to_state 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 320s ok 26 /ssm/delayed/mark_completed 320s # Start of next tests 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 320s ok 27 /ssm/delayed/next/cancel 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 320s ok 28 /ssm/delayed/next/not_started 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 320s ok 29 /ssm/delayed/next/complete 320s # End of next tests 320s # Start of jump_to_state tests 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 320s ok 30 /ssm/delayed/jump_to_state/cancel 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 320s ok 31 /ssm/delayed/jump_to_state/not_started 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 320s ok 32 /ssm/delayed/jump_to_state/last 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 14 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state -10 320s ok 33 /ssm/delayed/jump_to_state/wrong 320s # End of jump_to_state tests 320s # Start of mark_completed tests 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 320s ok 34 /ssm/delayed/mark_completed/cancel 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 320s ok 35 /ssm/delayed/mark_completed/not_started 320s # End of mark_completed tests 320s # Start of cancel tests 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 320s ok 36 /ssm/delayed/cancel/error 320s # End of cancel tests 320s # End of delayed tests 320s # Start of subssm tests 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 1 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 320s ok 37 /ssm/subssm/start 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 320s # 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. 320s # 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. 320s # 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. 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later. 320s ok 38 /ssm/subssm/mark_failed 320s # Start of start tests 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 320s ok 39 /ssm/subssm/start/with_started 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 320s ok 40 /ssm/subssm/start/with_delayed 320s # End of start tests 320s # End of subssm tests 320s # Start of cleanup tests 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 320s ok 41 /ssm/cleanup/complete 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 320s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: non-cleanup 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 320s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 2 (cleanup) with error: cleanup 1 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 320s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 3 (cleanup) with error: cleanup 2 320s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: non-cleanup 320s ok 42 /ssm/cleanup/fail 320s # End of cleanup tests 320s # End of ssm tests 320s PASS: libfprint-2/fpi-ssm.test 320s Running test: libfprint-2/driver-uru4000-msv2.test 321s ** (umockdev-run:2375): DEBUG: 17:03:18.989: umockdev.vala:123: Created udev test bed /tmp/umockdev.6OZ1J2 321s ** (umockdev-run:2375): DEBUG: 17:03:18.989: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 321s ** (umockdev-run:2375): DEBUG: 17:03:18.990: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 321s ** (umockdev-run:2375): DEBUG: 17:03:18.992: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.6OZ1J2/dev/bus/usb/001/047 321s ** (umockdev-run:2375): DEBUG: 17:03:18.992: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 321s ** (umockdev-run:2375): DEBUG: 17:03:18.993: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 321s ** (umockdev-run:2375): DEBUG: 17:03:18.995: umockdev.vala:1411: create_node_for_device: creating file device /tmp/umockdev.6OZ1J2/dev/bus/usb/001/001 321s ** (umockdev-run:2375): DEBUG: 17:03:18.995: umockdev.vala:1297: parsing device description for /devices/pci0000:00/0000:00:14.0 321s ** (umockdev-run:2375): DEBUG: 17:03:18.995: umockdev.vala:1366: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 321s (process:2379): libfprint-context-DEBUG: 17:03:19.045: Initializing FpContext (libfprint version 1.94.7+tod1) 321s (process:2379): libfprint-tod-DEBUG: 17:03:19.045: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 321s (process:2379): libfprint-context-DEBUG: 17:03:19.047: No driver found for USB device 1D6B:0002 321s (process:2379): libfprint-device-DEBUG: 17:03:19.047: Device reported probe completion 321s (process:2379): libfprint-device-DEBUG: 17:03:19.047: Completing action FPI_DEVICE_ACTION_PROBE in idle! 321s (process:2379): libfprint-device-DEBUG: 17:03:19.047: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s libusb: error [op_handle_events] cannot find handle for fd 9 321s libusb: error [op_handle_events] cannot find handle for fd 9 321s libusb: error [op_handle_events] cannot find handle for fd 9 321s libusb: error [op_handle_events] cannot find handle for fd 9 321s libusb: error [op_handle_events] cannot find handle for fd 9 321s libusb: error [op_handle_events] cannot find handle for fd 9 321s libusb: error [op_handle_events] cannot find handle for fd 9 321s libusb: error [op_handle_events] cannot find handle for fd 9 321s libusb: error [op_handle_events] cannot find handle for fd 9 321s libusb: error [op_handle_events] cannot find handle for fd 9 321s libusb: error [op_handle_events] cannot find handle for fd 9 321s (process:2379): GLib-DEBUG: 17:03:19.049: setenv()/putenv() are not thread-safe and should not be used after threads are created 321s (process:2379): libfprint-image_device-DEBUG: 17:03:19.051: Image device open completed 321s (process:2379): libfprint-device-DEBUG: 17:03:19.051: Device reported open completion 321s (process:2379): libfprint-device-DEBUG: 17:03:19.051: Completing action FPI_DEVICE_ACTION_OPEN in idle! 321s (process:2379): libfprint-device-DEBUG: 17:03:19.051: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s (process:2379): libfprint-device-DEBUG: 17:03:19.052: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s (process:2379): libfprint-image_device-DEBUG: 17:03:19.052: Activating image device 321s (process:2379): libfprint-image_device-DEBUG: 17:03:19.052: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.052: [uru4000] INIT_NUM_STATES entering state 0 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.052: read 1 regs at 7 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.053: reg value 3 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.053: [uru4000] INIT_NUM_STATES entering state 1 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.053: [uru4000] INIT_NUM_STATES entering state 3 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.053: set 83 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.053: [uru4000] INIT_NUM_STATES entering state 4 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.053: [uru4000] POWERUP_NUM_STATES entering state 0 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.053: [uru4000] POWERUP_NUM_STATES entering state 1 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.053: set 03 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.054: [uru4000] POWERUP_NUM_STATES entering state 2 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.054: read 1 regs at 7 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.054: reg value 83 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.054: [uru4000] POWERUP_NUM_STATES entering state 3 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.054: [uru4000] POWERUP_NUM_STATES entering state 4 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.064: [uru4000] POWERUP_NUM_STATES entering state 5 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.064: 155049636: ../libfprint/drivers/uru4000.c:291 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.067: [uru4000] POWERUP_NUM_STATES entering state 6 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.067: [uru4000] POWERUP_NUM_STATES entering state 1 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.067: set 03 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.068: [uru4000] POWERUP_NUM_STATES entering state 2 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.068: read 1 regs at 7 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.068: reg value 3 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.068: [uru4000] POWERUP_NUM_STATES entering state 3 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.068: [uru4000] POWERUP_NUM_STATES completed successfully 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.068: [uru4000] INIT_NUM_STATES entering state 5 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.069: recv irq type 56aa 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.069: late scanpwr interrupt 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.069: [uru4000] INIT_NUM_STATES entering state 6 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.069: [uru4000] INIT_NUM_STATES entering state 7 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.069: read 16 regs at f0 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.069: reg value 50 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.069: [uru4000] INIT_NUM_STATES entering state 8 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.069: Versions 0059 and 0034 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.069: [uru4000] INIT_NUM_STATES completed successfully 321s (process:2379): libfprint-image_device-DEBUG: 17:03:19.069: Image device activation completed 321s (process:2379): libfprint-image_device-DEBUG: 17:03:19.069: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 321s (process:2379): libfprint-image_device-DEBUG: 17:03:19.069: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.069: wait finger on 321s (process:2379): libfprint-device-DEBUG: 17:03:19.069: Device reported finger status change: FP_FINGER_STATUS_NEEDED 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.070: recv irq type 0101 321s (process:2379): libfprint-device-DEBUG: 17:03:19.070: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 321s (process:2379): libfprint-image_device-DEBUG: 17:03:19.070: Image device reported finger status: on 321s (process:2379): libfprint-image_device-DEBUG: 17:03:19.070: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.070: starting capture 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.070: Image encryption seed: 1374298404 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.070: [uru4000] IMAGING_NUM_STATES entering state 0 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.071: [uru4000] IMAGING_NUM_STATES entering state 1 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.071: hw header lines 289 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.071: dev2: 10849 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.071: image seems to be encrypted 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.072: [uru4000] IMAGING_NUM_STATES entering state 2 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.072: read 4 regs at 34 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.072: reg value 7b 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.072: [uru4000] IMAGING_NUM_STATES entering state 3 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.072: encryption id 05 -> key db896f5f 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.072: 0 02 67 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.072: decoding 67 lines 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.072: 1 00 1 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.072: skipping 1 lines 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.072: 2 02 49 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.072: decoding 49 lines 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.073: 3 01 1 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.073: skipping 1 lines 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.073: 4 00 1 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.073: skipping 1 lines 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.073: 5 02 49 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.073: decoding 49 lines 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.073: 6 00 1 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.073: skipping 1 lines 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.073: 7 02 121 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.073: decoding 121 lines 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.073: [uru4000] IMAGING_NUM_STATES entering state 4 321s (process:2379): libfprint-image_device-DEBUG: 17:03:19.073: Image device captured an image 321s (process:2379): libfprint-image_device-DEBUG: 17:03:19.075: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 321s (process:2379): libfprint-device-DEBUG: 17:03:19.075: Device reported finger status change: FP_FINGER_STATUS_PRESENT 321s (process:2379): libfprint-SSM-DEBUG: 17:03:19.075: [uru4000] IMAGING_NUM_STATES completed successfully 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.075: await finger off 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.075: recv irq type 0200 321s (process:2379): libfprint-device-DEBUG: 17:03:19.075: Device reported finger status change: FP_FINGER_STATUS_NONE 321s (process:2379): libfprint-image_device-DEBUG: 17:03:19.075: Image device reported finger status: off 321s (process:2379): libfprint-image_device-DEBUG: 17:03:19.075: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 321s (process:2379): libfprint-image_device-DEBUG: 17:03:19.075: Deactivating image device 321s (process:2379): libfprint-image_device-DEBUG: 17:03:19.075: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.075: deactivating 321s (process:2379): libfprint-uru4000-DEBUG: 17:03:19.076: cancelled 321s (process:2379): libfprint-image_device-DEBUG: 17:03:19.076: Image device deactivation completed 321s (process:2379): libfprint-image_device-DEBUG: 17:03:19.076: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 321s (process:2379): libfprint-image-DEBUG: 17:03:19.146: Minutiae scan completed in 0.072949 secs 321s (process:2379): libfprint-device-DEBUG: 17:03:19.147: Device reported capture completion 321s (process:2379): libfprint-device-DEBUG: 17:03:19.147: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 321s (process:2379): libfprint-device-DEBUG: 17:03:19.147: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 321s (process:2379): libfprint-image_device-DEBUG: 17:03:19.149: Image device close completed 321s (process:2379): libfprint-device-DEBUG: 17:03:19.149: Device reported close completion 321s (process:2379): libfprint-device-DEBUG: 17:03:19.149: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 321s (process:2379): libfprint-device-DEBUG: 17:03:19.149: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 321s ** (umockdev-run:2375): DEBUG: 17:03:19.293: umockdev.vala:150: Removing test bed /tmp/umockdev.6OZ1J2 321s (umockdev-run:2375): GLib-DEBUG: 17:03:19.296: unsetenv() is not thread-safe and should not be used after threads are created 321s Comparing PNGs /tmp/libfprint-umockdev-test-5itp357u/capture.png and /usr/share/installed-tests/libfprint-2/uru4000-msv2/capture.png 321s PASS: libfprint-2/driver-uru4000-msv2.test 321s SUMMARY: total=33; passed=33; skipped=0; failed=0; user=18.8s; system=6.5s; maxrss=39612 321s autopkgtest [17:03:19]: test installed-tests: -----------------------] 329s installed-tests PASS 329s autopkgtest [17:03:27]: test installed-tests: - - - - - - - - - - results - - - - - - - - - - 330s autopkgtest [17:03:28]: @@@@@@@@@@@@@@@@@@@@ summary 330s installed-tests PASS 348s Creating nova instance adt-noble-arm64-libfprint-20240308-165758-juju-7f2275-prod-proposed-migration-environment-2 from image adt/ubuntu-noble-arm64-server-20240308.img (UUID 0a2e7fd3-7002-451c-9c23-d2e75949fe48)...