udisksd crashed with SIGSEGV in g_mutex_lock()

Bug #1722361 reported by starkus
This bug report is a duplicate of:  Edit Remove
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
udisks2 (Ubuntu)
New
Undecided
Unassigned

Bug Description

sorry, not sure.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: udisks2 2.6.5-2ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
Date: Mon Oct 9 19:31:06 2017
ExecutablePath: /usr/lib/udisks2/udisksd
InstallationDate: Installed on 2017-07-18 (82 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: System manufacturer System Product Name
ProcCmdline: /usr/lib/udisks2/udisksd
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=UUID=930d4a07-4aa3-4d13-91d3-f543b24f1157 ro quiet splash loglevel=2 vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f9b678735b5 <g_mutex_lock+5>: lock xadd %eax,(%rdi)
 PC (0x7f9b678735b5) 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 0x00007f9b678735b5 in g_mutex_lock () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 #1 0x00007f9b6782b240 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 #2 0x0000562d64e0e605 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 artful on 2017-08-13 (57 days ago)
UserGroups:

dmi.bios.date: 03/17/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1307
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H77-V LE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1307:bd03/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-VLE:rvrRevX.0x: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
starkus (starkus) 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.