udisksd crashed with SIGSEGV in g_mutex_lock()

Bug #1758763 reported by Jerry D,Hodge
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

18.4 bionic beaver

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: udisks2 2.7.6-2ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu1
Architecture: amd64
CustomUdevRuleFiles: 70-snap.pencilsheep.rules 70-snap.gitkraken.rules 70-snap.discord.rules 70-snap.core.rules
Date: Sun Mar 25 18:15:50 2018
ExecutablePath: /usr/lib/udisks2/udisksd
MachineType: MSI MS-7976
ProcCmdline: /usr/lib/udisks2/udisksd
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=0084e11e-8e42-4b53-b01f-a38b41b9b1b1 ro quiet splash vt.handoff=1
SegvAnalysis:
 Segfault happened at: 0x7fbdb05e0cd5 <g_mutex_lock+5>: lock xadd %eax,(%rdi)
 PC (0x7fbdb05e0cd5) ok
 source "%eax" ok
 destination "(%rdi)" (0x75736f6e2c777220) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: udisks2
Stacktrace:
 #0 0x00007fbdb05e0cd5 in g_mutex_lock () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 #1 0x00007fbdb0598520 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 #2 0x0000556d0cec0204 in main ()
StacktraceTop:
 g_mutex_lock () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 main ()
Title: udisksd crashed with SIGSEGV in g_mutex_lock()
UpgradeStatus: Upgraded to bionic on 2018-03-20 (5 days ago)
UserGroups:

dmi.bios.date: 04/25/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.I0
dmi.board.asset.tag: Default string
dmi.board.name: Z170A GAMING M7 (MS-7976)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.I0:bd04/25/2017:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: Default string
dmi.product.name: MS-7976
dmi.product.version: 1.0
dmi.sys.vendor: MSI

Revision history for this message
Jerry D,Hodge (jdbulletholes) 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.