devkit-disks-daemon crashed with SIGSEGV in dbus_g_method_return_error()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devicekit-disks (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: devicekit-disks
crashed during installation to an Flash Disk and/or SD/SDHC card .... installation works fine, seems to be only a ghost-bug during installation process
System - Ubuntu 9.10
devicekit-disks:
Nainštalovaná verzia: 007-2ubuntu2
Kandidát: 007-2ubuntu2
Tabuľka verzií:
*** 007-2ubuntu2 0
500 http://
100 /var/lib/
ProblemType: Crash
.etc.fstab:
aufs / aufs rw 0 0
tmpfs /tmp tmpfs nosuid,nodev 0 0
Architecture: i386
Date: Sun Oct 25 18:01:11 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
MachineType: TOSHIBA TECRA R10
Package: devicekit-disks 007-2ubuntu2
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /usr/lib/
ProcEnviron:
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0xf2cf1d <dbus_g_
PC (0x00f2cf1d) 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_
?? ()
?? ()
?? ()
?? ()
Title: devkit-disks-daemon crashed with SIGSEGV in dbus_g_
Uname: Linux 2.6.31-14-generic i686
UserGroups:
dmi.bios.date: 02/25/2009
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 1.50
dmi.board.
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.
dmi.modalias: dmi:bvnTOSHIBA:
dmi.product.name: TECRA R10
dmi.product.
dmi.sys.vendor: TOSHIBA
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.