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
i installed xubuntu for 4 friends from live cd and on 4th im now reporting this bug. while installing going all is good. when it was done and asked for restart crash report came up. now im reporting it.
ProblemType: Crash
.etc.fstab:
aufs / aufs rw 0 0
tmpfs /tmp tmpfs nosuid,nodev 0 0
Architecture: i386
Date: Sun Feb 28 22:45:39 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/
LiveMediaBuild: Xubuntu 9.10 "Karmic Koala" - Release i386 (20091028.3)
Lsusb:
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
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 002 Device 002: ID 04b4:0033 Cypress Semiconductor Corp.
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Package: devicekit-disks 007-2ubuntu3
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /usr/lib/
ProcEnviron:
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x4cef1d <dbus_g_
PC (0x004cef1d) 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/10/2003
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: SiS-651
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixT
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.