Benjamin Berg e3b0d52ce5 device: Catch client disconnect during Release ...

If the client disconnected while the release call was stopping the
current action, then the disconnect will be processed. This means that
the device can be closed already and the session is destroyed.

Add a check for this, in the same way that the vanished handler deals
with this corner case.

2021-08-11 08:58:26 +00:00

..

dbus-interactive-auth.patch

build: Generate fprintd dbus sources using interactive flags

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

device.c

device: Catch client disconnect during Release

2021-08-11 08:58:26 +00:00

device.xml

device: Do not allow enrolling a finger that is already enrolled

2021-04-02 00:22:16 +02:00

file_storage.c

file_storage: Ensure username/finger match our expectations

2021-07-30 23:52:00 +02:00

file_storage.h

fprintd: Reindent the source code following uncrustify rules

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

fprintd.h

Implement suspend/resume handling

2021-08-09 13:25:11 +02:00

main.c

main: De-init the storage when main loop is over

2021-03-03 19:51:07 +01:00

manager.c

Implement suspend/resume handling

2021-08-09 13:25:11 +02: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