udisksd crashed with SIGSEGV in g_mutex_lock()

Bug #1748566 reported by MARLON RIBEIRO MEDEIROS
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

ok

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: udisks2 2.6.5-2ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
CustomUdevRuleFiles: 70-snap.chromium.rules 70-snap.gimp.rules 70-snap.core.rules
Date: Fri Feb 9 21:39:55 2018
ExecutablePath: /usr/lib/udisks2/udisksd
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/udisks2/udisksd
ProcEnviron:
 LANG=pt_BR.UTF-8
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=16eefb51-d5fd-4cf3-a058-0e697c718ad6 ro quiet splash
SegvAnalysis:
 Segfault happened at: 0x7f5f71d365b5 <g_mutex_lock+5>: lock xadd %eax,(%rdi)
 PC (0x7f5f71d365b5) 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
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 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.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH P67
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd11/01/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHP67:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
MARLON RIBEIRO MEDEIROS (marlonrib) 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.