i already did it device sde in the previous message
On 4 April 2014 21:57, Phillip Susi <email address hidden> 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: > gpartedbin crashed with SIGSEGV in _int_free() > > Status in "gparted" package in Ubuntu: > New > > Bug description: > crashes as soon as it appears followins password entry > > ProblemType: Crash > DistroRelease: Ubuntu 14.04 > Package: gparted 0.18.0-1 > ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 > Uname: Linux 3.13.0-23-generic x86_64 > ApportVersion: 2.14-0ubuntu1 > Architecture: amd64 > Date: Fri Apr 4 19:23:15 2014 > ExecutablePath: /usr/sbin/gpartedbin > InstallationDate: Installed on 2014-04-04 (0 days ago) > InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 > (20140115) > ProcCmdline: /usr/sbin/gpartedbin > SegvAnalysis: > Segfault happened at: 0x7f3d389b1f6f <_int_free+527>: cmp > 0x18(%rax),%r13 > PC (0x7f3d389b1f6f) ok > source "0x18(%rax)" (0xbcd08e1000b912) not located in a known VMA > region (needed readable region)! > destination "%r13" ok > Stack memory exhausted (SP below stack segment) > SegvReason: reading unknown VMA > Signal: 11 > SourcePackage: gparted > StacktraceTop: > _int_free (av=0x7f3d1c000020, p=<optimised out>, have_lock=0) at > malloc.c:3996 > ped_exception_catch () from /lib/x86_64-linux-gnu/libparted.so.0 > ped_exception_throw () from /lib/x86_64-linux-gnu/libparted.so.0 > fat_boot_sector_read () from /lib/x86_64-linux-gnu/libparted.so.0 > fat_probe () from /lib/x86_64-linux-gnu/libparted.so.0 > Title: gpartedbin crashed with SIGSEGV in _int_free() > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1302762/+subscriptions >
-- Cliff Tinker
i already did it device sde in the previous message
On 4 April 2014 21:57, Phillip Susi <email address hidden> wrote:
> Can you run fdisk -l with this drive plugged in? /bugs.launchpad .net/bugs/ 1302762 ature: Ubuntu 3.13.0- 23.45-generic 3.13.8 gpartedbin gpartedbin 64-linux- gnu/libparted. so.0 64-linux- gnu/libparted. so.0 sector_ read () from /lib/x86_ 64-linux- gnu/libparted. so.0 64-linux- gnu/libparted. so.0 /bugs.launchpad .net/ubuntu/ +source/ gparted/ +bug/1302762/ +subscriptions
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> gpartedbin crashed with SIGSEGV in _int_free()
>
> Status in "gparted" package in Ubuntu:
> New
>
> Bug description:
> crashes as soon as it appears followins password entry
>
> ProblemType: Crash
> DistroRelease: Ubuntu 14.04
> Package: gparted 0.18.0-1
> ProcVersionSign
> Uname: Linux 3.13.0-23-generic x86_64
> ApportVersion: 2.14-0ubuntu1
> Architecture: amd64
> Date: Fri Apr 4 19:23:15 2014
> ExecutablePath: /usr/sbin/
> InstallationDate: Installed on 2014-04-04 (0 days ago)
> InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64
> (20140115)
> ProcCmdline: /usr/sbin/
> SegvAnalysis:
> Segfault happened at: 0x7f3d389b1f6f <_int_free+527>: cmp
> 0x18(%rax),%r13
> PC (0x7f3d389b1f6f) ok
> source "0x18(%rax)" (0xbcd08e1000b912) not located in a known VMA
> region (needed readable region)!
> destination "%r13" ok
> Stack memory exhausted (SP below stack segment)
> SegvReason: reading unknown VMA
> Signal: 11
> SourcePackage: gparted
> StacktraceTop:
> _int_free (av=0x7f3d1c000020, p=<optimised out>, have_lock=0) at
> malloc.c:3996
> ped_exception_catch () from /lib/x86_
> ped_exception_throw () from /lib/x86_
> fat_boot_
> fat_probe () from /lib/x86_
> Title: gpartedbin crashed with SIGSEGV in _int_free()
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups:
>
> To manage notifications about this bug go to:
>
> https:/
>
--
Cliff Tinker