[Bug 1450180] Re: gparted crashes immediately after started

It's weird that reports cannot be forwarded. Anyway, I created a new one: https://bugs.launchpad.net/ubuntu-gnome/+bug/1457056 This report can be closed. Thanks for your support Plillip! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubunt

[Bug 1450180] Re: gparted crashes immediately after started

Nope... launchpad can't be used to track bugs in PPAs... you might email them though at gnome3-t...@lists.launchpad.net . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450180 Title: gparted crashe

[Bug 1450180] Re: gparted crashes immediately after started

Yes, right, there is libglibmm-2.4-1c2a - libglibmm-2.4-1c2a | 2.43.2-0ubuntu1~vivid1 (gnome3-staging) - libglibmm-2.4-1c2a | 2.42.0-1 (ubuntu) (I was mistaken with libgtkmm, in my comment earlier) I downgraded libglibmm to 2.42 from Ubuntu, and gparted works. Thanks for your help! So coul

[Bug 1450180] Re: gparted crashes immediately after started

If I got it right, these are the ones coming from gnome3-staging ppa libatk1.0-0 | 2.16.0-0ubuntu1~vivid1 libgdk-pixbuf2.0-0 | 2.31.1-1~utopic1 libglib2.0-0 | 2.44.0-0ubuntu1~vivid0 libglibmm-2.4-1c2a | 2.43.2-0ubuntu1~vivid1Packages libpango-1.0-0 | 1.36.7-1~utopic1 libpangocairo-1.0-0 | 1.36.7-1

[Bug 1450180] Re: gparted crashes immediately after started

Weird... can you go through the list of libs from ldd and see if any of them are from the ppa instead of the official archive? There must be one somewhere, and it apparently isn't libgtkmm itself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 1450180] Re: gparted crashes immediately after started

Like this? $ debsums libgtkmm-2.4-1c2a /usr/lib/i386-linux-gnu/libgdkmm-2.4.so.1.1.0 OK /usr/lib/i386-linux-gnu/libgtkmm-2.4.so.1.1.0 OK /usr/share/doc/libgtkmm-2.4-1c2a/AUTHORS OK /usr/share/doc/l

[Bug 1450180] Re: gparted crashes immediately after started

Can you check the md5sum of /usr/lib/i386-linux-gnu/libgtkmm-2.4.so.1? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450180 Title: gparted crashes immediately after started To manage notifications

[Bug 1450180] Re: gparted crashes immediately after started

$ ldd `which gpartedbin` linux-gate.so.1 => (0xb7701000) libparted.so.2 => /lib/i386-linux-gnu/libparted.so.2 (0xb7681000) libparted-fs-resize.so.0 => /lib/i386-linux-gnu/libparted-fs-resize.so.0 (0xb7661000) libgtkmm-2.4.so.1 => /usr/lib/i386-linux-gnu/libgtkmm-2.

[Bug 1450180] Re: gparted crashes immediately after started

Hrm... I had assumed that the gtk3 ppa included a newer version of libgtkmm-2.4-1c2a since this bug is not present in version 2.24.4 ( it was introduced upstream in a later version and subsequently fixed ). Can you run ldd `which gpartedbin`? -- You received this bug notification because you are

[Bug 1450180] Re: gparted crashes immediately after started

Phillip, I certainly missed something, but, as far as I can understand, 1. gparted does not use gtk 3 2. gparted uses gtk 2 3. gparted, libgtk-2 and ligtkmm-2 are provided by Ubuntu $ apt-cache madison gparted libgtk2.0-0 libgtkmm-2.4-1c2a gparted | 0.19.0-2 | http://fr.archive.ubuntu.com/ub

[Bug 1450180] Re: gparted crashes immediately after started

gparted uses glibmm which had this bug occur and was fixed upstream. If the gnome3 ppa is shipping a version that still has the bug, you should let them know as they will need to fix it. Since it isn't part of Ubuntu there's nothing we can do. ** Changed in: glibmm2.4 (Ubuntu) Status: In

[Bug 1450180] Re: gparted crashes immediately after started

> Ubuntu does not ship gtk 3.16, hence my question as to where you got it. OK! I have GNOME3 ppa enabled, that pulls gtk 3.16 indeed. How is it related to gparted? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad

[Bug 1450180] Re: gparted crashes immediately after started

Ubuntu does not ship gtk 3.16, hence my question as to where you got it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450180 Title: gparted crashes immediately after started To manage notificatio

[Bug 1450180] Re: gparted crashes immediately after started

But OK, what Srdjan suggests in Comment #10 seems to be the root cause. (any rationale to think otherwise?) The bug was acknowledged and fixed upstream: - https://bugzilla.gnome.org/show_bug.cgi?id=743466#c4 - https://git.gnome.org/browse/glibmm/commit/?id=10e24926a149c8dbfbc5853b2d4ff5a4cd50bc

[Bug 1450180] Re: gparted crashes immediately after started

> So you mean you have third party or self built packages installed? if this is addressed to me (?), the answer is no. (see also my Comment #14) On my system, gparted and gtkmm come from 'http://fr.archive.ubuntu.com/ubuntu/ vivid/main' As far as I can see, gparted in Ubuntu 15.04 is using GTK2

[Bug 1450180] Re: gparted crashes immediately after started

So you mean you have third party or self built packages installed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450180 Title: gparted crashes immediately after started To manage notifications abo

[Bug 1450180] Re: gparted crashes immediately after started

> you need gtk 3.16 installed for this to happen. my gparted uses gtk-2. Do you mean that without gtk-3 on the system, gparted works? Package: gparted Version: 0.19.0-2 Depends: libglib2.0-0 (>= 2.12.0), libglibmm-2.4-1c2a (>= 2.42.0), libgtk2.0-0 (>= 2.14.0), libgtkmm-2.4-1c2a (>= 1:2.24.0)

[Bug 1450180] Re: gparted crashes immediately after started

Since no one here bothered to mention... you need gtk 3.16 installed for this to happen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450180 Title: gparted crashes immediately after started To ma

[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

[Bug 1450180] Re: gparted crashes immediately after started

I wonder if you are really having the same issue as srdjan? Can you try running gdb like he did? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450180 Title: gparted crashes immediately after start

[Bug 1450180] Re: gparted crashes immediately after started

I believe that I have standard packages $ apt-cache showpkg libgtkmm-2.4-1c2a Package: libgtkmm-2.4-1c2a Versions: 1:2.24.4-1.1 (/var/lib/apt/lists/fr.archive.ubuntu.com_ubuntu_dists_vivid_main_binary-i386_Packages) (/var/lib/dpkg/status) $ debsums libgtkmm-2.4-1c2a /usr/lib/i386-linux-gnu/li

[Bug 1450180] Re: gparted crashes immediately after started

So I'm not able to reproduce this on vivid, are you running a non standard version of libgtkmm? ** Changed in: glibmm2.4 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad

[Bug 1450180] Re: gparted crashes immediately after started

Looks like the bug is in glibmm so assigning a task there. Hopefully that upstream patch can get applied quickly. ** Also affects: glibmm2.4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed t

[Bug 1450180] Re: gparted crashes immediately after started

Do you know when this will land in ubuntu? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450180 Title: gparted crashes immediately after started To manage notifications about this bug go to: https

[Bug 1450180] Re: gparted crashes immediately after started

** Changed in: gparted Status: Unknown => Fix Released ** Changed in: gparted Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450180 Title: gparted crashes im

[Bug 1450180] Re: gparted crashes immediately after started

Probably related: https://bugzilla.gnome.org/show_bug.cgi?id=743466 They seem to have a patch upstream for glibmm ** Bug watch added: GNOME Bug Tracker #743466 https://bugzilla.gnome.org/show_bug.cgi?id=743466 ** Also affects: gparted via https://bugzilla.gnome.org/show_bug.cgi?id=743466

[Bug 1450180] Re: gparted crashes immediately after started

I meant to debsum your entire system, not just gparted, as most likely one of your libraries is corrupt. Valgrind is also complaining about bad CRCs on a number of libraries, indicating that they are corrupt. -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1450180] Re: gparted crashes immediately after started

Log: sudo valgrind -v gpartedbin ** Attachment added: "valgring_on_gpartedbin" https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1450180/+attachment/4388412/+files/log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. http

[Bug 1450180] Re: gparted crashes immediately after started

@Philip: Yeah, I found that it runs with a script after the initial post which is why I hid it but gpartedbin is really having issues and valgrind log was run on the binary and not the launcher. $ debsums gparted /usr/bin/gparted-pkexec OK /usr

[Bug 1450180] Re: gparted crashes immediately after started

gparted is a shell script that runs the real program, gpartedbin. Your valgrind run on gparted just debugged the shell ( dash ) instead of gparted itself. Can you install the debsums package and verify that none of your libraries are corrupt? ** Changed in: gparted (Ubuntu) Status: Confi

[Bug 1450180] Re: gparted crashes immediately after started

Looks like it might be a bad FD? ** Attachment added: "valgrind log" https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1450180/+attachment/4388008/+files/log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.la

[Bug 1450180] Re: gparted crashes immediately after started

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gparted (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450180 Title: gp

[Bug 1450180] Re: gparted crashes immediately after started

sudo gdb gpartedbin GNU gdb (Ubuntu 7.9-1ubuntu1) 7.9 Copyright (C) 2015 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

[Bug 1450180] Re: gparted crashes immediately after started

gparted (different from gpartedbin code posted above) also doesn't look like an ELF file: readelf -a /usr/sbin/gparted readelf: Error: Not an ELF file - it has the wrong magic bytes at the start dpkg -l | grep gparted ii gparted 0.19.0-2