← Back to team overview

desktop-packages team mailing list archive

[Bug 1450180] Re: gparted crashes immediately after started

 

I get pretty much the same output

$ sudo gdb gpartedbin 
...
...
Reading symbols from 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/i386-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0xb7b24506 in Glib::wrap_register(unsigned long, Glib::ObjectBase* (*)(_GObject*)) () from /usr/lib/i386-linux-gnu/libglibmm-2.4.so.1

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glibmm2.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1450180

Title:
  gparted crashes immediately after started

Status in Gnome Partition Editor:
  Fix Released
Status in glibmm2.4 package in Ubuntu:
  Incomplete
Status in gparted package in Ubuntu:
  Incomplete

Bug description:
  gparted immediately segfaults after launch...

  $ sudo gparted
  [sudo] password for me: 
  Segmentation fault (core dumped)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gparted 0.19.0-2
  Uname: Linux 4.1.0-040100rc1-generic i686
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Wed Apr 29 21:53:15 2015
  InstallationDate: Installed on 2014-06-17 (316 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found.
  SourcePackage: gparted
  UpgradeStatus: Upgraded to vivid on 2015-04-27 (2 days ago)

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