Public bug reported: [ 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. ** Affects: libfprint (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1992841 Title: Same symbols are exposed in libraries causing potential GType issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1992841/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
