Benjamin Berg 7c9a04c2ae device: Fix race when client vanishes from bus ...

We have a condition where a client vanishing instead of cleaning up the
operation using VerifyStop would cause fprintd to hang. This only
happens if the underlying enroll/verify/identify operation has already
finished when the client vanishes.

Fix this by correctly interpreting current_cancellable as a flag for
these operations.

Fixes: #97

2021-01-04 11:00:18 +01:00

..

dbus-interactive-auth.patch

build: Generate fprintd dbus sources using interactive flags

2020-12-07 15:14:07 +01:00

device.c

device: Fix race when client vanishes from bus

2021-01-04 11:00:18 +01:00

device.xml

fprintd: Use GDBus codegen based implementation

2020-11-10 14:45:59 +01:00

file_storage.c

fprintd: Reindent the source code following uncrustify rules

2020-12-07 18:41:45 +01:00

file_storage.h

fprintd: Reindent the source code following uncrustify rules

2020-12-07 18:41:45 +01:00

fprintd.h

Add compatibility defines to allow compiling with older glib

2020-12-14 11:30:45 +01:00

main.c

fprintd: Reindent the source code following uncrustify rules

2020-12-07 18:41:45 +01:00

manager.c

manager: Do not use unnecessary volatile qualifier on GQuark

2020-12-19 22:34:12 +01:00

manager.xml

fprintd: Use GDBus codegen based implementation

2020-11-10 14:45:59 +01:00

meson.build

build: Generate fprintd dbus sources using interactive flags

2020-12-07 15:14:07 +01:00

storage.h

fprintd: Reindent the source code following uncrustify rules

2020-12-07 18:41:45 +01:00