[Bug 362917] Re: Unable to determine the partition number.

2009-12-14 Thread drcmcs
I get this problem in Karmic. -- Unable to determine the partition number. https://bugs.launchpad.net/bugs/362917 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 362917] Re: Unable to determine the partition number.

2009-12-08 Thread mohan
dgdfg ** Changed in: usb-creator (Ubuntu) Assignee: (unassigned) = mohan (usarajmohan) ** Changed in: usb-creator (Ubuntu) Assignee: mohan (usarajmohan) = (unassigned) -- Unable to determine the partition number. https://bugs.launchpad.net/bugs/362917 You received this bug

[Bug 362917] Re: Unable to determine the partition number.

2009-09-25 Thread Evan Dandrea
This is fixed in Karmic as usb-creator now uses the attribute given by devicekit-disks to determine the partition number. ** Changed in: usb-creator (Ubuntu) Status: Confirmed = Fix Released -- Unable to determine the partition number. https://bugs.launchpad.net/bugs/362917 You received

[Bug 362917] Re: Unable to determine the partition number.

2009-08-07 Thread Andreas Schildbach
For me, the workaround does not work. I always get the message '/dev/sdb is too full to fit Ubuntu 9.10 (700.7 MB more needed)'. The 'Open' button is ignored. In the 'Other...' dialog when I press on 'Desktop', I get the root user desktop (which does not exist) rather than the logged in user

[Bug 362917] Re: Unable to determine the partition number.

2009-06-28 Thread Victor
I can confirm this too. -- Unable to determine the partition number. https://bugs.launchpad.net/bugs/362917 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 362917] Re: Unable to determine the partition number.

2009-05-21 Thread Erik van Oosten
I can confirm that creating a partitiontable with gparted works. -- Unable to determine the partition number. https://bugs.launchpad.net/bugs/362917 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 362917] Re: Unable to determine the partition number.

2009-04-28 Thread LeoRochael
This issue happens with usb-storage devices formatted without a partition-table. This same problem is alluded to in bug #277865. A workaround is to create a partition table and a new partition with GParted. The proper fix is for usb-creator to be able to copy the installation into a drive

[Bug 362917] Re: Unable to determine the partition number.

2009-04-27 Thread Colan Schwartz
Confirming. ** Changed in: usb-creator (Ubuntu) Status: New = Confirmed -- Unable to determine the partition number. https://bugs.launchpad.net/bugs/362917 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing

[Bug 362917] Re: Unable to determine the partition number.

2009-04-17 Thread Sebastien Bacher
I'm using current jaunty, the key is a new 8Gb one -- Starting up at 15:20:02 -- [15:20:02] /var/lib/python-support/python2.6/dbus/connection.py:242: DeprecationWarning: object.__init__() takes no parameters super(Connection, self).__init__(*args, **kwargs) [15:20:02] new device: {'udi':

[Bug 362917] Re: Unable to determine the partition number.

2009-04-17 Thread Evan Dandrea
Can you please attach the output of hal-device with the USB disk plugged in? Thanks! -- Unable to determine the partition number. https://bugs.launchpad.net/bugs/362917 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs

[Bug 362917] Re: Unable to determine the partition number.

2009-04-17 Thread Sebastien Bacher
I guess you are interested by the usb key log? ** Attachment added: diff before and after inserting the key http://launchpadlibrarian.net/25625729/usbcreator -- Unable to determine the partition number. https://bugs.launchpad.net/bugs/362917 You received this bug notification because you are