fprintd crashed with SIGSEGV

Bug #1960588 reported by Daniel van Vugt
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fprintd (Ubuntu)
New
Undecided
Unassigned

Bug Description

Needs retracing

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: fprintd 1.94.1-1
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Feb 9 10:53:14 2022
ExecutablePath: /usr/libexec/fprintd
InstallationDate: Installed on 2021-11-05 (97 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103)
ProcCmdline: /usr/libexec/fprintd
SegvAnalysis:
 Segfault happened at: 0x7f0c7552a55f: call *%rax
 PC (0x7f0c7552a55f) ok
 source "*%rax" (0x45aeb1e2d1524e2c) not located in a known VMA region (needed readable region)!
 destination "(%rsp)" (0x7ffd2ca1b040) ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: fprintd
StacktraceTop:
 () at /lib/x86_64-linux-gnu/libusb-1.0.so.0
 () at /lib/x86_64-linux-gnu/libusb-1.0.so.0
 libusb_unref_device () at /lib/x86_64-linux-gnu/libusb-1.0.so.0
 () at /lib/x86_64-linux-gnu/libgusb.so.2
 g_object_unref () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: fprintd crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
separator:

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Close enough to bug 1960387.

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1960387, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.