Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the stable
release - Oneiric Ocelot. It would help us greatly if you could test
with it so we can work on getting it fixed. You can find out more about
the development release at http://www.ubuntu.com/testing/ . Thanks again
and we appreciate your help.
** Changed in: gnome-disk-utility (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-disk-utility (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/735396
Title:
Error starting job: Failed to fork (Cannot allocate memory)
Status in “gnome-disk-utility” package in Ubuntu:
Incomplete
Bug description:
Binary package hint: gnome-disk-utility
I tried to delete the partition of an old usb stick (64Mb!), because I wanted
to try out the "Benchmark" test of Disk Utility.
(The usb pen drive is some sort of thing to get wireless internet on a
laptop, so perhaps it is some hardware problem)
However, when I try to delete the partition I get a screen saying:
"
Error deleting partion
An error occurred while performing an operation on "USB064Mb" (Partition 1 of
USB2.0 FlashDisk): The operation failed
Details
Error starting job: Failed to fork (Cannot allocate memory)
"
The entire systems gets a bit laggy..
*Then after a while (when I am filling in this bug report!) I try to delete
the partition again, and this time: no error message and the partition seems to
be deleted.... Weird..
**Now, I tried to run the Read/Write benchmark. However, I again get an
error, this time:
"
Error benchmarking drive
An error occurred while performing on operation on "USB2.0 FlashDisk" (USB2.0
FlashDisk): The operation failed
Details
A partition table was detected - write benchmarking requires the disk to be
completely empty
"
***Again, while I am typing this: I try the Read-Only Benchmark --> and this
works fine..
Can it be that something on the drive is blocking attempts to write data
to it?
I don't understand the fork error and the read/write issue...
Please advice if you need more info: I am fairly new to reporting bugs
(this way).
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: gnome-disk-utility 2.30.1-2
ProcVersionSignature: Ubuntu 2.6.35-27.48-generic 2.6.35.11
Uname: Linux 2.6.35-27-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Tue Mar 15 11:42:17 2011
ExecutablePath: /usr/bin/palimpsest
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: gnome-disk-utility
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/735396/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
