[Bug 1376051] Re: gpartedbin crashed with SIGABRT in g_assertion_message()

[A. Eibach]

OK...I take it back...

The actual reason was that IDIOTIC and illogical naming.

I will never understand why a _fully published_ version of gparted in
Utopic is called 0.19.0-1___build___1 and your still somewhat unofficial
PPA-only version is called 0.19.0-1-___ubuntu___1.

Normally, the x.yy.z-p-ubuntuQ naming ought to be used for releases that are in the *standard* distribution, and not the PPA. It is always way better to indicate certain builds of packages coming from a PPA by using an appropriate filename (at least not the above one, that's for sure).
So JFTR, at the moment, 0.19.0-1build1 is the (non-working, crap)  version shipped with Utopic, whilst 0.19.0-1ubuntu1 is the (working) PPA version. Just to get this clear for further readers running into this extremely time-consuming problem.

BTW sorry for the rude tone, but I've really wasted way too much
pointless time with this stuff now, and that---may I quote the
description---so-called "minor regression". I'd burst out laughing, if
it wasn't so pathetic...? That oh-so "minor" regression will be enough
for me for months again...

Mind you all of you, "essential tools with little bugs" and "essential tools that do not run at all" is not quite the same thing...
Lastly: YES 0.19.0-1ubuntu1 is the first version that works again since 0.18.x. Good Lord...don't get  me started about the QA here therefore...

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gparted in Ubuntu.
https://bugs.launchpad.net/bugs/1376051

Title:
  gpartedbin crashed with SIGABRT in g_assertion_message()

Status in Gnome Partition Editor:
  Incomplete
Status in gparted package in Ubuntu:
  Confirmed

Bug description:
  [SRU REQUEST]

  [Impact]

  Program crashes or otherwise has erratic behavior when applying
  operations due to a cross thread write after free that was introduced
  in this upstream release.  Upstream has already applied this fix after
  others discovered the issue and verified the fix.

  [Test Case]

  Apply various operations to disk, such as resizing and moving
  filesystems.  Sometimes it works, sometimes it crashes.  The original
  report below is an example of one way in which it may crash.

  [Regression Potential]

  Minimal; patch already upstream.

  
  I'm working with vfat.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: gparted 0.19.0-1build1
  ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
  Uname: Linux 3.16.0-18-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  Date: Tue Sep 30 20:35:28 2014
  ExecutablePath: /usr/sbin/gpartedbin
  InstallationDate: Installed on 2014-09-25 (5 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
  ProcCmdline: /usr/sbin/gpartedbin
  Signal: 6
  SourcePackage: gparted
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gpartedbin crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gparted/+bug/1376051/+subscriptions