udisksd crashed with SIGSEGV in g_mutex_lock()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
udisks2 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: udisks2 2.6.5-2ubuntu1
Uname: Linux 4.13.0-
ApportVersion: 2.20.6-0ubuntu6
Architecture: amd64
CustomUdevRuleF
Date: Sun Aug 20 18:59:53 2017
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2017-04-18 (124 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcCmdline: /usr/lib/
ProcEnviron:
LANG=en_CA.UTF-8
LANGUAGE=en_CA:en
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7fa7934ab515 <g_mutex_lock+5>: lock xadd %eax,(%rdi)
PC (0x7fa7934ab515) ok
source "%eax" ok
destination "(%rdi)" (0x74616c65722c
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 artful on 2017-04-29 (113 days ago)
UserGroups:
dmi.bios.date: 07/15/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2
dmi.board.
dmi.board.name: 990FXA-UD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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.