From c828522f3f428f6a372c58e36c2c19204a1d18a6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Marco=20Trevisan=20=28Trevi=C3=B1o=29?= <mail@3v1n0.net>
Date: Thu, 16 Jan 2020 19:09:20 +0100
Subject: [PATCH 180/181] synaptics: Really check if a print is device database

Fix a typo causing the not-in-database print error to be fired, actually
checking the response result.
---
 libfprint/drivers/synaptics/synaptics.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libfprint/drivers/synaptics/synaptics.c b/libfprint/drivers/synaptics/synaptics.c
index 2aac75e..3f79e4b 100644
--- a/libfprint/drivers/synaptics/synaptics.c
+++ b/libfprint/drivers/synaptics/synaptics.c
@@ -634,7 +634,7 @@ verify_msg_cb (FpiDeviceSynaptics *self,
           self->cmd_complete_data = GINT_TO_POINTER (FPI_MATCH_FAIL);
           self->cmd_complete_error = NULL;
         }
-      else if (BMKT_FP_DATABASE_NO_RECORD_EXISTS)
+      else if (resp->result == BMKT_FP_DATABASE_NO_RECORD_EXISTS)
         {
           fp_info ("Print is not in database");
           fpi_device_verify_complete (device,
-- 
2.24.1