udisks-daemon crashed with SIGSEGV in g_main_dispatch()

Bug #1219688 reported by Dimitri John Ledkov
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
udisks (Ubuntu)
New
Undecided
Unassigned

Bug Description

crash...

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: udisks 1.0.4-8
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Fri Aug 30 13:03:21 2013
ExecutablePath: /usr/lib/udisks/udisks-daemon
InstallationDate: Installed on 2012-01-12 (598 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
MarkForUpload: True
ProcCmdline: /usr/lib/udisks/udisks-daemon
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic.efi.signed root=UUID=6669d411-80c3-41cc-a629-ad84e1ee6854 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x40ac92: mov 0x10(%rax),%rdi
 PC (0x0040ac92) ok
 source "0x10(%rax)" (0xaaaaaaaaaaaaaaba) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: udisks
StacktraceTop:
 ?? ()
 ?? ()
 g_main_dispatch (context=0x15eaaa0) at /build/buildd/glib2.0-2.37.6/./glib/gmain.c:3065
 g_main_context_dispatch (context=context@entry=0x15eaaa0) at /build/buildd/glib2.0-2.37.6/./glib/gmain.c:3641
 g_main_context_iterate (context=0x15eaaa0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimised out>) at /build/buildd/glib2.0-2.37.6/./glib/gmain.c:3712
Title: udisks-daemon crashed with SIGSEGV in g_main_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: utah
dmi.bios.date: 10/24/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F16
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z77X-D3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
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.:bvrF16:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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
Dimitri John Ledkov (xnox) 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 #980368, 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.

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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