Processed: Re: Bug#819488: gparted crash with a libparted backtrace

2016-11-03 Thread Debian Bug Tracking System 
Processing control commands:

> severity -1 important
Bug #819488 [src:parted] gparted crash with a libparted backtrace
Severity set to 'important' from 'grave'

-- 
819488: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#819488: gparted crash with a libparted backtrace

2016-11-03 Thread Sandro Tosi 
control: severity -1 important

On Thu, Nov 3, 2016 at 1:48 PM, Mattia Rizzolo  wrote:
> On Thu, Nov 03, 2016 at 11:37:02AM -0400, Sandro Tosi wrote:
>> Mattia, do you still consider this bug RC? thanks!
>
> I don't think so, no.  Though it's still a crash, it's important, but
> probably not RC indeed.

yup agreed on this, setting the severity accordingly


On Thu, Nov 3, 2016 at 4:34 PM, Phil Susi  wrote:
> On 11/3/2016 11:37 AM, Sandro Tosi wrote:
>> Phillip, did you have a chance to look at making parted not crashing
>> if there is only one unallocated sector between partitions? Mattia, do
>> you still consider this bug RC? thanks!
>
> I have not had time to work on it yet.

no worries!


-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#819488: gparted crash with a libparted backtrace

2016-11-03 Thread Phil Susi 
On 11/3/2016 11:37 AM, Sandro Tosi wrote:
> Phillip, did you have a chance to look at making parted not crashing
> if there is only one unallocated sector between partitions? Mattia, do
> you still consider this bug RC? thanks!

I have not had time to work on it yet.

Bug#819488: gparted crash with a libparted backtrace

2016-11-03 Thread Mattia Rizzolo 
On Thu, Nov 03, 2016 at 11:37:02AM -0400, Sandro Tosi wrote:
> Mattia, do you still consider this bug RC? thanks!

I don't think so, no.  Though it's still a crash, it's important, but
probably not RC indeed.

Furthermore I'm not affected by this anymore, since I "fixed" my
partition table to have libparted like it more.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#819488: gparted crash with a libparted backtrace

2016-11-03 Thread Sandro Tosi 
On Mon, 11 Apr 2016 21:00:41 -0400 Phillip Susi  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 04/11/2016 02:13 PM, Mattia Rizzolo wrote:
> > On Mon, Apr 11, 2016 at 11:52:32AM -0600, Curtis Gedak wrote:
> >> If I recall correctly, libparted was not able to handle when
> >> there was only one unallocated sector between logical partitions
> >> (it expects at least two).
>
> I believe that is exactly it Curtis.
>
> > well, that's really not a reason to crash like that! ;)
>
> For the last 3 decades, it has not been a problem since every disk
> partitioner has worked this way.  I have sen a few bug reports about
> this recently though, and the others have reported using something
> called Easeus disk partitioning software.  Have you used this?  It
> would be good to confirm this is the source of the problem and I'll
> see if I can't fix parted to handle it.

Phillip, did you have a chance to look at making parted not crashing
if there is only one unallocated sector between partitions? Mattia, do
you still consider this bug RC? thanks!

Bug#819488: gparted crash with a libparted backtrace

2016-04-12 Thread Mattia Rizzolo 
On Mon, Apr 11, 2016 at 09:00:41PM -0400, Phillip Susi wrote:
> I have sen a few bug reports about this recently though,

good to know I'm not the only one!  I was in fact quite uneasy seeing
there were no reports in the BTS. :)

> and the others have reported using something
> called Easeus disk partitioning software.  Have you used this?

never heard of this thing.

> It
> would be good to confirm this is the source of the problem and I'll
> see if I can't fix parted to handle it.

tbh, I experienced this crash since quite some time, but I was always
too lazy to open a bug.
I have this hard disc with this partitioning since Feb 2015, and never
changed anything since then.

I don't recall how I made the partitions, sorry, but for sure I haven't
used that software I've never heard about.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#819488: gparted crash with a libparted backtrace

2016-04-11 Thread Phillip Susi 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 04/11/2016 02:13 PM, Mattia Rizzolo wrote:
> On Mon, Apr 11, 2016 at 11:52:32AM -0600, Curtis Gedak wrote:
>> If I recall correctly, libparted was not able to handle when
>> there was only one unallocated sector between logical partitions
>> (it expects at least two).

I believe that is exactly it Curtis.

> well, that's really not a reason to crash like that! ;)

For the last 3 decades, it has not been a problem since every disk
partitioner has worked this way.  I have sen a few bug reports about
this recently though, and the others have reported using something
called Easeus disk partitioning software.  Have you used this?  It
would be good to confirm this is the source of the problem and I'll
see if I can't fix parted to handle it.


-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCgAGBQJXDEi5AAoJEBB5UWFcu6UW1cgH/2ReOLJAbvtm6ZCVLd+S8VFG
/T42BG64dbtp5PEEeLt+fE7hYRQkTb+Kmnv5YEApJ39Sucihi3yx2EWUqwxmEZ9Y
QElVEbIBB82GUJtGEIhgOiCZKfSvqyDocOZ6Gm4n8ZQScOEzKMeNCb48F1mTBc5i
CVlCS1ynlfa0IoYqSx4EwH2K5Q6CNQhQiOrJtvGkiXryp7GkVwt37lrOpuR0z+D0
jThfBq7ULE7YPUXEgIwquBpxUWaHvU2eQdSKAhS9mQ4DvoAyHkn+YCWy8z5yjkE8
iY6uCMw70mtnG0nTF+m52TBbRb4KTrRno4MuF+2OMFttTyLVyblOFCm8bp08/7Y=
=wouG
-END PGP SIGNATURE-

Bug#819488: gparted crash with a libparted backtrace

2016-04-11 Thread Mattia Rizzolo 
On Mon, Apr 11, 2016 at 11:52:32AM -0600, Curtis Gedak wrote:
> If I recall correctly, libparted was not able to handle when there was
> only one unallocated sector between logical partitions (it expects at
> least two).

well, that's really not a reason to crash like that! ;)

> To work around the problem you might consider deleting the Linux Swap
> sda7 partition using fdisk.

yes, I could recreate the swap partition.  now, I'm not in hurry to
havev gparted working, so I'm just gonna postpone this till I either
need it, or if you need a confirmation that's the issue (but then I
won't be able to test a fix, etc).

> Next you could recreate the Linux Swap making sure to leave at least two
> unallocated sectors after sda6.  Then you would need to ensure that the
> UUID for the Linux Swap matched the value in /etc/fstab so that it would
> automatically be mounted at boot time.

Yeah, I have a vague idea about partitions and /etc/fstab ;)

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#819488: gparted crash with a libparted backtrace

2016-04-11 Thread Curtis Gedak 
On 16-04-11 11:42 AM, Mattia Rizzolo wrote:
> 
> Device Boot  StartEndSectors   Size Id Type
> /dev/sda1  *  2046 1953523711 1953521666 931.5G  5 Extended
> /dev/sda5 2048  99487  97440 476.9G 83 Linux
> /dev/sda6   1873524736 1933524991   6256  28.6G 83 Linux
> /dev/sda7   1933524992 1953523711   19998720   9.5G 82 Linux swap / 
> Solaris
> 
> Partition 1 does not start on physical sector boundary.


If I recall correctly, libparted was not able to handle when there was
only one unallocated sector between logical partitions (it expects at
least two).

In your situation there is only one unallocated sector between the end
of sda6 and the start of sda7.  The unallocated sector is used to store
the Extended Boot Record for a logical partition.

To work around the problem you might consider deleting the Linux Swap
sda7 partition using fdisk.

Next you could recreate the Linux Swap making sure to leave at least two
unallocated sectors after sda6.  Then you would need to ensure that the
UUID for the Linux Swap matched the value in /etc/fstab so that it would
automatically be mounted at boot time.

Regards,
Curtis

Bug#819488: gparted crash with a libparted backtrace

2016-04-11 Thread Mattia Rizzolo 
control: reassign -1 src:parted 3.2-15

On Mon, Apr 11, 2016 at 11:06:14AM -0600, Curtis Gedak wrote:
> Would you be able to provide the output from the following two commands?

sure thing :)

> sudo fdisk -l -u

mattia@chase ~ % sudo fdisk -l -u
[sudo] password for mattia: 
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xbfbc6f0d

Device Boot  StartEndSectors   Size Id Type
/dev/sda1  *  2046 1953523711 1953521666 931.5G  5 Extended
/dev/sda5 2048  99487  97440 476.9G 83 Linux
/dev/sda6   1873524736 1933524991   6256  28.6G 83 Linux
/dev/sda7   1933524992 1953523711   19998720   9.5G 82 Linux swap / Solaris

Partition 1 does not start on physical sector boundary.




Disk /dev/mapper/home: 476.9 GiB, 511996592128 bytes, 93344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


> sudo parted /path-to-your-device unit s print

mattia@chase ~ % sudo parted /dev/sda unit s print
Backtrace has 15 calls on stack:
  15: /lib/x86_64-linux-gnu/libparted.so.2(ped_assert+0x44) [0x7f79c46fbae4]
  14: /lib/x86_64-linux-gnu/libparted.so.2(+0x2009f) [0x7f79c470f09f]
  13: /lib/x86_64-linux-gnu/libparted.so.2(+0x114fa) [0x7f79c47004fa]
  12: /lib/x86_64-linux-gnu/libparted.so.2(ped_disk_add_partition+0x25f) 
[0x7f79c4700def]
  11: /lib/x86_64-linux-gnu/libparted.so.2(+0x1f98f) [0x7f79c470e98f]
  10: /lib/x86_64-linux-gnu/libparted.so.2(+0x1fa20) [0x7f79c470ea20]
  9: /lib/x86_64-linux-gnu/libparted.so.2(+0x1fa20) [0x7f79c470ea20]
  8: /lib/x86_64-linux-gnu/libparted.so.2(+0x1f9c9) [0x7f79c470e9c9]
  7: /lib/x86_64-linux-gnu/libparted.so.2(+0x209b5) [0x7f79c470f9b5]
  6: /lib/x86_64-linux-gnu/libparted.so.2(ped_disk_new+0x48) [0x7f79c4700a18]
  5: parted(+0x7343) [0x56338d485343]
  4: parted(non_interactive_mode+0x92) [0x56338d48b102]
  3: parted(main+0x1238) [0x56338d484028]
  2: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f79c3ef7610]
  1: parted(_start+0x29) [0x56338d4841d9]


You found a bug in GNU Parted! Here's what you have to do:

Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:

Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:

http://ftp.gnu.org/gnu/parted/

Please check this version prior to bug reporting.

If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:

http://www.gnu.org/software/parted

for further information.

Your report should contain the version of this release (3.2)
along with the error message below, the output of

parted DEVICE unit co print unit s print

and the following history of commands you entered.
Also include any additional information about your setup you
consider important.

Assertion (metadata_length > 0) at ../../../libparted/labels/dos.c:2313 in 
function add_logical_part_metadata() failed.

[1]17350 abort  sudo parted /dev/sda unit s print
134 mattia@chase ~ %

(134 is the return code)

> I expect that latter command to fail if the problem is indeed in the
> libparted library.

So, it seems it is :)

Reassigning to src:parted.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Processed: Re: Bug#819488: gparted crash with a libparted backtrace

2016-04-11 Thread Debian Bug Tracking System 
Processing control commands:

> reassign -1 src:parted 3.2-15
Bug #819488 [gparted] gparted crash with a libparted backtrace
Bug reassigned from package 'gparted' to 'src:parted'.
No longer marked as found in versions gparted/0.25.0-1.
Ignoring request to alter fixed versions of bug #819488 to the same values 
previously set
Bug #819488 [src:parted] gparted crash with a libparted backtrace
Marked as found in versions parted/3.2-15.

-- 
819488: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#819488: gparted crash with a libparted backtrace

2016-04-11 Thread Curtis Gedak 
Would you be able to provide the output from the following two commands?

sudo fdisk -l -u

  where one of the options is a lower case "L" and not the number one.

sudo parted /path-to-your-device unit s print

  where /path-to-your-device is something like /dev/sda.

I expect that latter command to fail if the problem is indeed in the
libparted library.

Regards,
Curtis

Bug#819488: gparted crash with a libparted backtrace

2016-03-29 Thread Mattia Rizzolo 
Package: gparted
Version: 0.25.0-1
Severity: grave

mattia@chase ~ % gksudo gparted
==
libparted : 3.2
==
Backtrace has 16 calls on stack:
  16: /lib/x86_64-linux-gnu/libparted.so.2(ped_assert+0x44) [0x7fc5feb2eae4]
  15: /lib/x86_64-linux-gnu/libparted.so.2(+0x2009f) [0x7fc5feb4209f]
  14: /lib/x86_64-linux-gnu/libparted.so.2(+0x114fa) [0x7fc5feb334fa]
  13: /lib/x86_64-linux-gnu/libparted.so.2(ped_disk_add_partition+0x25f) 
[0x7fc5feb33def]
  12: /lib/x86_64-linux-gnu/libparted.so.2(+0x1f98f) [0x7fc5feb4198f]
  11: /lib/x86_64-linux-gnu/libparted.so.2(+0x1fa20) [0x7fc5feb41a20]
  10: /lib/x86_64-linux-gnu/libparted.so.2(+0x1fa20) [0x7fc5feb41a20]
  9: /lib/x86_64-linux-gnu/libparted.so.2(+0x1f9c9) [0x7fc5feb419c9]
  8: /lib/x86_64-linux-gnu/libparted.so.2(+0x209b5) [0x7fc5feb429b5]
  7: /lib/x86_64-linux-gnu/libparted.so.2(ped_disk_new+0x48) [0x7fc5feb33a18]
  6: /usr/sbin/gpartedbin() [0x466bfe]
  5: /usr/sbin/gpartedbin() [0x47554e]
  4: /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1(+0x51c3d) [0x7fc600043c3d]
  3: /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x70b75) [0x7fc5feff7b75]
  2: /lib/x86_64-linux-gnu/libpthread.so.0(+0x7454) [0x7fc5fde78454]
  1: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7fc5fdbb5edd]


And quit here, funnily exiting with 0 (e.g. successfully).

Now, unhelpfully the maintainer did a binary upload, either built with
an outdated chroot or by manually disabling the automatic debug
packages, but given that probably the issue is in libparted2, and luckiy
the parted's maintainer does source uploads, and built the debug
package, I installed libparted2-dbgsym, and run the this in gdb to have
a backtrace, here follows the whole thing.

I don't know if the issue actually lies, so maybe this bug should be
reassigned to libparted2 instead.

Please tell me if you would be helped by more information.

mattia@chase ~ % sudo gdb /usr/sbin/gpartedbin
GNU gdb (Debian 7.10-1+b1) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/sbin/gpartedbin...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/sbin/gpartedbin 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
==
libparted : 3.2
==
[New Thread 0x7fffee642700 (LWP 19548)]
[New Thread 0x7fffeda6b700 (LWP 19554)]
Backtrace has 16 calls on stack:
  16: /lib/x86_64-linux-gnu/libparted.so.2(ped_assert+0x44) [0x75993ae4]
  15: /lib/x86_64-linux-gnu/libparted.so.2(+0x2009f) [0x759a709f]
  14: /lib/x86_64-linux-gnu/libparted.so.2(+0x114fa) [0x759984fa]
  13: /lib/x86_64-linux-gnu/libparted.so.2(ped_disk_add_partition+0x25f) 
[0x75998def]
  12: /lib/x86_64-linux-gnu/libparted.so.2(+0x1f98f) [0x759a698f]
  11: /lib/x86_64-linux-gnu/libparted.so.2(+0x1fa20) [0x759a6a20]
  10: /lib/x86_64-linux-gnu/libparted.so.2(+0x1fa20) [0x759a6a20]
  9: /lib/x86_64-linux-gnu/libparted.so.2(+0x1f9c9) [0x759a69c9]
  8: /lib/x86_64-linux-gnu/libparted.so.2(+0x209b5) [0x759a79b5]
  7: /lib/x86_64-linux-gnu/libparted.so.2(ped_disk_new+0x48) [0x75998a18]
  6: /usr/sbin/gpartedbin() [0x466bfe]
  5: /usr/sbin/gpartedbin() [0x47554e]
  4: /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1(+0x51c3d) [0x76ea8c3d]
  3: /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x70b75) [0x75e5cb75]
  2: /lib/x86_64-linux-gnu/libpthread.so.0(+0x7454) [0x74cdd454]
  1: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x74a1aedd]
Assertion (metadata_length > 0) at ../../../libparted/labels/dos.c:2313 in 
function add_logical_part_metadata() failed.

Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffeda6b700 (LWP 19554)]
0x74965478 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:55
55  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  0x74965478 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:55
#1  0x749668fa in __GI_abort () at abort.c:89
#2  0x75993b9c in ped_assert (cond_text=cond_text@entry=0x759becce 
"metadata_length > 0", 
file=file@entry=0x759beac0 "../../../libparted/labels/dos.c", 
line=line@entry=2313, 
function=function@entry=0x759bf040 <__PRETTY_FUNCTION__.5892>