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

[Omegamormegil]

Binary package hint: devicekit-disks

I got a crash notification during the installation of the Ubuntu 9.10 RC while running it as a LiveUSB.

ProblemType: Crash
.etc.fstab:
 aufs / aufs rw 0 0
 tmpfs /tmp tmpfs nosuid,nodev 0 0
Architecture: i386
Date: Thu Oct 22 17:27:11 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/devicekit-disks/devkit-disks-daemon
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
MachineType: Dell Inc. Inspiron 910
NonfreeKernelModules: wl
Package: devicekit-disks 007-2ubuntu2
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --
ProcCmdline: /usr/lib/devicekit-disks/devkit-disks-daemon
ProcEnviron:

ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x323f1d <dbus_g_method_return_error+29>: mov 0x10(%esi),%edi
 PC (0x00323f1d) 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: 12/29/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: CN0J14
dmi.board.vendor: Dell Inc.
dmi.board.version: A04
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A04
dmi.modalias: dmi:bvnDellInc.:bvrA04:bd12/29/2008:svnDellInc.:pnInspiron910:pvrA04:rvnDellInc.:rnCN0J14:rvrA04:cvnDellInc.:ct8:cvrA04:
dmi.product.name: Inspiron 910
dmi.product.version: A04
dmi.sys.vendor: Dell Inc.

[Ian (superian)]

I have lost the various debug info (sorry - the wireless network died on the LiveCD session) but this happened to me too.

Installing 9.10 RC, using the CD, on a Compaq Deskpro.

Same 'source "0x10(%esi)" (0x00000010) not located in a known VMA region (needed readable region)!' error.

On restarting the PC after the installation finished, the partitions took a very long time to mount, with much scrolling of error messages on the graphical splash screen.

[Ian Mackenzie (gldcompsol)]

Installing Ubuntu 9.10 i386 RC from CD on socket 754 Sempron64 system with 512MB + NVidia 5200 AGP card.

Manual disk partitioning to overwrite the gradually upgraded 9.10 Alpha version with a fresh install.
Ian Mackenzie

[Jan Owoc (jsowoc)]

I will add a "me too" to this bug.

Ubuntu 9.10 RC netbook remix on EEE PC 701.
It happened right after startup, before I had a chance to do anyting.

[papukaija (papukaija)]

I'm also confirming this bug. For me this bug happened while I was installing Ubuntu 9.10 RC. The installer was at around 30% (copying files) and I had Firefox opened too. I partitioned the disk manually (to make a separate home partition) before runnining the installer.

[lazychris2000 (lazychris2000)]

For me, it crashed during installation when I got to setting up partitions in ubiquity--running off the live cd to install 9.10 RC.
The partition screen was blank and I got the spinning pinwheel cursor for a few seconds when the error message came up. Nothing was open except the installation window. It did the same thing whether I booted from the live cd and told it 'install ubuntu' or 'run ubuntu without making changes to the system'.
Core 2 Quad Q6600 (not overclocked)
Intel brand motherboard
2GB (4x512MB) PC4200
GeForce 7200GS (it may be a 7300GS)
250GB Western Digital SATA drive

[papukaija (papukaija)]

Where can I find the error messages displayed in the graphical boot loader?

[Apport retracing service (apport)]

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.

[papukaija (papukaija)]

Please set the visibility of bug 452208 to public.