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
this happened suddenly, when I was using live cd
ProblemType: Crash
.etc.fstab:
aufs / aufs rw 0 0
tmpfs /tmp tmpfs nosuid,nodev 0 0
/dev/sda4 swap swap defaults 0 0
Architecture: amd64
Date: Sat Oct 24 03:06:11 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release Candidate amd64 (20091020.3)
Lsusb:
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0bda:0151 Realtek Semiconductor Corp. Mass Stroage Device
Bus 001 Device 002: ID 05dc:a731 Lexar Media, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP-Pavilion FK964AA-ABM a6615la
Package: devicekit-disks 007-2ubuntu2
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /usr/lib/
ProcEnviron:
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x7f4d5635407e <dbus_g_
PC (0x7f4d5635407e) ok
source "0x20(%rdi)" (0x00000020) not located in a known VMA region (needed readable region)!
destination "%r8d" 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 x86_64
UserGroups:
dmi.bios.date: 04/23/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.17
dmi.board.name: Nettle3
dmi.board.vendor: ECS
dmi.board.version: 2.2
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: FK964AA-ABM a6615la
dmi.sys.vendor: HP-Pavilion
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.