Same symbols are exposed in libraries causing potential GType issues

[Marco Trevisan (Treviño)]

[ Impact ]

Both libfprint-2.so and libfprint-2.so.2.0.0 and libfprint-2-tod.so.1 (that the first one loads) are defining some symbols instead of just referencing them.

This can lead to hangs, or deadlocks because we could try to re-define the same GType multiple times.

See more details at:
  https://gitlab.freedesktop.org/3v1n0/libfprint/-/merge_requests/2

[ Test case ]

 1. Download this script:
    https://gitlab.freedesktop.org/3v1n0/libfprint/-/raw/tod/libfprint/tod/tests/check-library-symbols.sh
 2. Run it as:
    libfprint/tod/tests/check-library-symbols.sh \
      /usr/lib/x86_64-linux-gnu/libfprint-2.so.2 \
      /usr/lib/x86_64-linux-gnu/libfprint-2-tod.so.1
 3. Ensure that no duplicated symbols are shown

[ Regression potential ]

Shared libraries linking with libfprint (or tod) may not find symbols.

[Launchpad Janitor (janitor)]

This bug was fixed in the package libfprint - 1:1.94.5+tod1-0ubuntu1

---------------
libfprint (1:1.94.5+tod1-0ubuntu1) kinetic; urgency=medium

  * New upstream release (LP: #1992855):
    - Supports new FPC MOC device
    - Avoid defining duplicated symbols in tod and libfprint (LP: #1992841)
  * debian/libfprint-2-2.postinst: Devices triggers updated
  * debian/patches: Drop all (applied upstream)
  * debian/libfprint-2-tod1.symbols: Add new symbols for shared drivers
  * debian/source: Remove include-binaries file, we've none now

 -- Marco Trevisan (Treviño) <email address hidden> Fri, 14 Oct 2022 00:18:27 +0200