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

A. Eibach 1376051 at bugs.launchpad.net
Mon Dec 15 01:45:21 UTC 2014


Bingo, because I can confirm FOR SURE that 0.19.0-1-ubuntu1 does NOT include the fix for this _critical_ bug here at all!
Left to say, I'm sick and tired of finding the 0.19.0somethingbuildsomething crap everywhere.

*It* *is* *simply* *unuseable*. Full stop.

I had to move my butt to ubuntuupdates.org to get the 0.19.1 release, which works great, but is virtually unavailable elsewhere.
The same I can also recommend to you desperate users, for the waiting is really a little bit too long now.  
How long are we still supposed to wait? Spring 2015 ?? 

This has nothing to do with impatience; the bug described in #1376051 is *SO* critical that I have to revert to 0.18.x otherwise.
PPA sometimes feels like a home for the elderly recently, needing dozens of nudges to get things going there...

Plus, a lot of those PPAs you'd find there are already available in the
*standard* distros. However, people would usually move over to PPA to
find packages *NOT YET* in distros. When one finds greatly the very same
stuff in there again, there is no point of having a PPA to your
disposal.

-- 
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



More information about the foundations-bugs mailing list