partition resizer daemon crashes while resizing a partition (Installation from USBStick, created with Unetbootin)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devicekit-disks (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: devicekit-disks
Ubuntu 9.10 Netbook Remix x86
I created A bootable USB Stick with Unetbootin, and booted my laptop. I started the installation, and selected to resize an existing partition (Backtrack 4 pre final was allready installed). the partition resizer started, but at 50% nothing happened anymore and finally it crashed after a while.
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: Wed Dec 30 16:21:47 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/
LiveMediaBuild: Ubuntu-
MachineType: ASUSTeK Computer INC. 1008HA
Package: devicekit-disks 007-2ubuntu3
ProcCmdLine: initrd=/ubninit file=/cdrom/
ProcCmdline: /usr/lib/
ProcEnviron:
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x371f1d <dbus_g_
PC (0x00371f1d) 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_
?? ()
?? ()
?? ()
?? ()
Tags: ubuntu-unr
Title: devkit-disks-daemon crashed with SIGSEGV in dbus_g_
Uname: Linux 2.6.31-14-generic i686
UserGroups:
dmi.bios.date: 04/27/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0302
dmi.board.
dmi.board.name: 1008HA
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: 1008HA
dmi.product.
dmi.sys.vendor: ASUSTeK Computer INC.
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.