It isn't the same error message at all... there is nothing in what you
posted that is at all similar to previous comments in this thread.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302762
Title:
Phillip: OK, I'll file another bug report on this issue. However,
because of the identical error message showing up, I thought you would
be interested in seeing this report. I hoped that it would throw some
additional light onto what might actually be the source of the problem.
Regards.
--
You
Jeffery, your issue is completely unrelated to this bug or to gparted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302762
Title:
gpartedbin crashed with SIGSEGV in _int_free()
To manage notifica
Hardware: Asus U56E
Upgrade from Xubuntu 13.10 64-bit to 14.04 64-bit
I just upgraded to 14.04 and I also have this problem. During the
upgrade, I received the above error multiple times. Here is an excerpt
from /var/log/apt/term.log:
OK, I see, I'll use mkfs.msdos instead. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302762
Title:
gpartedbin crashed with SIGSEGV in _int_free()
To manage notifications about this bug go
Yes, don't use mkpartfs, that's unrelated to this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302762
Title:
gpartedbin crashed with SIGSEGV in _int_free()
To manage notifications about this
oh well, blame parted for screwing up big time by removing the possibility to
create filesystems post 2.4.
Upstream is many versions ahead and I guess those bugs have been fixed upstream
since quite some time, but backporting all this to a version that is usable by
distributions is almost impos
The crash can also be reproduced even without an real device, replace
/dev/sdc with a normal file name, such as './block', can also reproduce
it.
Here is the crash output from parted:
WARNING: you are attempting to use parted to operate on (mkpartfs) a file
system.
parted's file system manipulat
parted 2.3-19 will crash in my env:
# /dev/sdc is device name of my usb stick
sudo dd if=/dev/zero of=/dev/sdc
sudo parted -s /dev/sdc mklabel gpt
sudo parted -a minimal -s /dev/sdc mkpartfs 'EFI' fat32 0 50
please find the details in the attached crash report
** Attachment added: "_sbin_parted.
I am not trying to get it from a mirror, but from the main archive...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302762
Title:
gpartedbin crashed with SIGSEGV in _int_free()
To manage notificat
Never mind, now I see it, thanks for the quick fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302762
Title:
gpartedbin crashed with SIGSEGV in _int_free()
To manage notifications about this bu
It can take a few hours to replicate to all of the mirrors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302762
Title:
gpartedbin crashed with SIGSEGV in _int_free()
To manage notifications about
Fix released, but there is nothing in the Trusty repos so far?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302762
Title:
gpartedbin crashed with SIGSEGV in _int_free()
To manage notifications ab
This bug was fixed in the package parted - 2.3-19
---
parted (2.3-19) unstable; urgency=medium
[ Phillip Susi ]
* fat-ntfs-large-sectors.patch: Fix fat and ntfs detection on non 512 byte
sectors (closes: #743816, LP: #1302762).
-- Colin Watson Tue, 08 Apr 2014 12:55:59 +0
** Branch linked: lp:ubuntu/trusty-proposed/parted
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302762
Title:
gpartedbin crashed with SIGSEGV in _int_free()
To manage notifications about this bug
** Changed in: parted (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302762
Title:
gpartedbin crashed with SIGSEGV in _int_free()
To manage notifications
** Branch linked: lp:debian/parted
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302762
Title:
gpartedbin crashed with SIGSEGV in _int_free()
To manage notifications about this bug go to:
https://
Please also see the information in bug #1303693, marked as dupplicate of
this one
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302762
Title:
gpartedbin crashed with SIGSEGV in _int_free()
To mana
** Changed in: parted (Ubuntu)
Importance: Medium => Critical
** Also affects: parted (Ubuntu Trusty)
Importance: Critical
Assignee: Phillip Susi (psusi)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Changed in: parted (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302762
Title:
gpartedbin crashed with SIGSEGV in _int_free()
To manage notifications abou
** Package changed: gparted (Ubuntu) => parted (Ubuntu)
** Changed in: parted (Ubuntu)
Status: Confirmed => In Progress
** Changed in: parted (Ubuntu)
Assignee: (unassigned) => Phillip Susi (psusi)
** Bug watch added: Debian Bug tracker #743816
http://bugs.debian.org/cgi-bin/bugre
Strange, are you sure that is the correct disk? It looks like that is
an ntfs partition, not fat, which is what parted was complaining about.
I did notice that it says that disk uses 4k sectors. I thought that dd
was supposed to default to the sector size of the drive so it should
have given 4k,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gparted (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302762
Title:
gp
merlin@gallahad:~$ sudo dd if=/dev/sde1 count=1 2>/dev/null | xxd
000: eb52 904e 5446 5320 2020 2000 1001 .R.NTFS.
010: 00f8 3f00 ff00 f801 ?...
020: 8000 8000 bf10 1c1d
030: 0400 5f0
Please run sudo dd if=/dev/sde1 count=1 2>/dev/null | xxd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302762
Title:
gpartedbin crashed with SIGSEGV in _int_free()
To manage notifications about t
i already did it device sde in the previous message
On 4 April 2014 21:57, Phillip Susi wrote:
> Can you run fdisk -l with this drive plugged in?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1302762
>
> Title:
>
Disk /dev/sda: 128.0 GB, 128035676160 bytes
255 heads, 63 sectors/track, 15566 cylinders, total 250069680 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00079235
Device Boo
Can you run fdisk -l with this drive plugged in?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302762
Title:
gpartedbin crashed with SIGSEGV in _int_free()
To manage notifications about this bug g
the fault appears to be caused by my hitachi external 2tb drive.as soon as i
powered off the drive gparted is working normally again.
if this drive is running when the system boots it reports bad secor size (i
have tried formating this drive in different filesystem's but it seems not to
cure the
Interesting... how about fdisk -l?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302762
Title:
gpartedbin crashed with SIGSEGV in _int_free()
To manage notifications about this bug go to:
https://
merlin@gallahad:~$ sudo parted -l
[sudo] password for merlin:
Model: ATA M4-CT128M4SSD2 (scsi)
Disk /dev/sda: 128GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start EndSizeType File system Flags
1 1049kB 111GB 111GB primary ext4
Can you run sudo parted -l and post the output?
It looks like you have a broken, or at least very unusual fat partition
somewhere.
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
32 matches
Mail list logo