devkit-disks-daemon crashed with SIGSEGV in dbus_g_method_return_error()

Bug #458401 reported by Christoph
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
devicekit-disks (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: devicekit-disks

The problem happens during the installation of 9.10 RC

ProblemType: Crash
.etc.fstab:
 aufs / aufs rw 0 0
 tmpfs /tmp tmpfs nosuid,nodev 0 0
 /dev/sda5 swap swap defaults 0 0
Architecture: i386
Date: Thu Oct 22 20:07:16 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/devicekit-disks/devkit-disks-daemon
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTeK Computer Inc. W1N
Package: devicekit-disks 007-2ubuntu2
PccardctlStatus:
 Socket 0:
   3.3V 16-bit PC Card
   Subdevice 0 (function 0) bound to driver "sdricoh_cs"
 Socket 1:
   no card
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de console-setup/layoutcode?=de
ProcCmdline: /usr/lib/devicekit-disks/devkit-disks-daemon
ProcEnviron:

ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x6b0f1d <dbus_g_method_return_error+29>: mov 0x10(%esi),%edi
 PC (0x006b0f1d) ok
 source "0x10(%esi)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: devicekit-disks
StacktraceTop:
 dbus_g_method_return_error ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: devkit-disks-daemon crashed with SIGSEGV in dbus_g_method_return_error()
Uname: Linux 2.6.31-14-generic i686
UserGroups:

dmi.bios.date: 05/26/2004
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0203
dmi.board.name: W1N
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0203:bd05/26/2004:svnASUSTeKComputerInc.:pnW1N:pvr1.0:rvnASUSTeKComputerInc.:rnW1N:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: W1N
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

Revision history for this message
Christoph (chr-istoph) 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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #452208, 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.

visibility: private → public
tags: removed: need-i386-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.