Marco Trevisan (Treviño) 2b81184b42 device: Fail with any non-zero return value on storage print_data_save() ...

When saving the prints we use g_file_set_contents under the hood and in
case return its error code that is a positive value.

So in such case we don't fail if we have a write failure at the end of
the enrollment.

While we could ensure in file storage to always return a negative value,
it's always better to ensure that is has to be 0 when we didn't get an
error.

Add a test checking for this case.

2021-01-27 17:52:05 +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: Fail with any non-zero return value on storage print_data_save()

2021-01-27 17:52:05 +01:00

device.xml

device: Throw an error if we failed to delete a device storage print

2021-01-22 15:19:21 +01:00

file_storage.c

file_storage: Cleanup the user storage path when removing prints

2021-01-05 13:07:19 +01:00

file_storage.h

fprintd: Reindent the source code following uncrustify rules

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

fprintd.h

device: Throw an error if we failed to delete a device storage print

2021-01-22 15:19:21 +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