udisksd crashed with SIGSEGV in g_mutex_lock()

Bug #1711959 reported by TheMixtureMedia
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
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-041300rc1-generic x86_64
ApportVersion: 2.20.6-0ubuntu6
Architecture: amd64
CustomUdevRuleFiles: 70-snap.core.rules
Date: Sun Aug 20 18:59:53 2017
ExecutablePath: /usr/lib/udisks2/udisksd
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/udisks2/udisksd
ProcEnviron:
 LANG=en_CA.UTF-8
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-041300rc1-generic root=UUID=fe023630-0df4-48c1-b410-9ce60622c6d1 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7fa7934ab515 <g_mutex_lock+5>: lock xadd %eax,(%rdi)
 PC (0x7fa7934ab515) ok
 source "%eax" ok
 destination "(%rdi)" (0x74616c65722c6365) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: udisks2
StacktraceTop:
 g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 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.asset.tag: To be filled by O.E.M.
dmi.board.name: 990FXA-UD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/15/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD3:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
TheMixtureMedia (mpmckinnon) wrote :
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 #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.

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.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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