Bug 203270 - [security/libfprint] pam_fprint fails every two times with a GLib-error
Summary: [security/libfprint] pam_fprint fails every two times with a GLib-error
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-gnome (Nobody)
Depends on:
Reported: 2015-09-22 21:26 UTC by Juan Ramón Molina Menor
Modified: 2020-12-19 14:38 UTC (History)
4 users (show)

See Also:
bugzilla: maintainer-feedback? (lichray)


Note You need to log in before you can comment on or make changes to this bug.
Description Juan Ramón Molina Menor 2015-09-22 21:26:16 UTC
FreeBSD-CURRENT r288108, libfprint-0.6.0 and pam_fprint-20080330_1. Not using fprint_demo.

One time in two, pam_fprint_enroll, login or su fail with the following error:

(process:1232): GLib-ERROR **: gmem.c:134: failed to allocate 18446744073709551612 bytes
Trace/BPT trap

The following execution of pam_fprint_enroll, login or su work (as long as the fingerprint is recognized, which is not always easy!). This "fails every two times" is strictly repeatable.

The fingerprint reader is recognized as a Validity VFS5011 on my Lenovo ThinkPad S440.

I have only found another reference to this error:
Comment 1 Martin Wilke freebsd_committer 2015-12-24 21:10:54 UTC
Over to glib maintainers
Comment 2 Walter Schwarzenfeld freebsd_triage 2018-01-13 01:10:48 UTC
Is this still relevant, or could it be closed?
Comment 3 Juan Ramón Molina Menor 2018-01-13 14:00:52 UTC
I have not tested it in a while. I’ll do it as soon as possible an report back.
Comment 4 Juan Ramón Molina Menor 2018-01-13 17:32:40 UTC
The error persists with a quite current system:

FreeBSD 12.0-CURRENT r326497 (Dec 3 2017).

I upgraded the fprint ports, but they are still at the same major version:

And GLib: glib-2.50.2_7,1
Comment 5 Tobias Kortkamp freebsd_committer 2018-10-05 11:12:36 UTC
(In reply to Juan Ramón Molina Menor from comment #4)
Still a problem with libfprint-0.7.0 and glib-2.56.1_1,1 ?
Comment 6 Juan Ramón Molina Menor 2018-10-08 12:07:24 UTC
(In reply to Tobias Kortkamp from comment #5)
Yes, the problem persists once every two tries. I have just updated the system to 12-ALPHA8 and upgraded the packages.

(process:1044): GLib-ERROR **: 14:01:40.427: gmem.c:136: failed to allocate 18446744073709551612 bytes
Comment 7 Tobias C. Berner freebsd_committer 2020-12-19 14:38:24 UTC
Moin moin 

Please re-open if this is still an issue.

mfg Tobias