udisksd crashed with SIGSEGV in g_mutex_lock()

Bug #1716169 reported by Антон Дерлюк
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
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
Date: Sun Sep 10 01:15:35 2017
ExecutablePath: /usr/lib/udisks2/udisksd
InstallationDate: Installed on 2017-06-18 (83 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170618)
MachineType: TOSHIBA Satellite L850-B5K
ProcCmdline: /usr/lib/udisks2/udisksd
ProcEnviron:
 LANG=ru_RU.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic root=UUID=3d21d2e0-2971-45b8-ab7e-9c82865d09fb ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f0780bf4565 <g_mutex_lock+5>: lock xadd %eax,(%rdi)
 PC (0x7f0780bf4565) 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: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 07/17/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.70
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name1
dmi.board.vendor: Type2 - Board Vendor Name1
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvr6.70:bd07/17/2013:svnTOSHIBA:pnSatelliteL850-B5K:pvrPSKDLR-03U00VRU:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.family: Type1Family
dmi.product.name: Satellite L850-B5K
dmi.product.version: PSKDLR-03U00VRU
dmi.sys.vendor: TOSHIBA

Revision history for this message
Антон Дерлюк (gespenst-vs) 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.