udisksd crashed with SIGSEGV in g_mutex_lock()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
udisks2 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
ok
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: udisks2 2.6.5-2ubuntu3
ProcVersionSign
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
CustomUdevRuleF
Date: Fri Feb 9 21:39:55 2018
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2018-02-04 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: System manufacturer System Product Name
ProcCmdline: /usr/lib/
ProcEnviron:
LANG=pt_BR.UTF-8
LANGUAGE=
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f5f71d365b5 <g_mutex_lock+5>: lock xadd %eax,(%rdi)
PC (0x7f5f71d365b5) ok
source "%eax" ok
destination "(%rdi)" (0x75736f6e2c77
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: udisks2
StacktraceTop:
g_mutex_lock () from /lib/x86_
?? () from /lib/x86_
main ()
Title: udisksd crashed with SIGSEGV in g_mutex_lock()
UpgradeStatus: Upgraded to bionic on 2018-02-08 (1 days ago)
UserGroups:
dmi.bios.date: 11/01/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3602
dmi.board.
dmi.board.name: SABERTOOTH P67
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
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 #1707451, 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.