** Tags added: testcase
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/617885
Title:
gparted crash at start: glibmm-ERROR **
To manage notifications about this bug go to:
Mark Ballenger, can you confirm the version of GParted that you are
using?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/617885
Title:
gparted crash at start: glibmm-ERROR **
--
ubuntu-bugs
Running netbook 10.10 from a live cd. Gparted starts then crashes immediately.
running sudo gparted outputs
glibmm-ERROR **;
unhandled exception (type std::exception) in signal handler:
what: basic_string::_S_Create
This started happening after I tried to backup a hd with PartImage is
not Ghost
Still having the bug with a Live USB stick made from unetbootin which
downloaded the latest 10.10 live-cd image.
Apt-cache fix didn't work here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/617885
MsG: i'm pretty sure your confusing things. There is no fix involving
apt-cache
There is a fixed package for maverick, just update it from the repo
(enable proposed updates), comment #79, e.g.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug was fixed in the package gparted - 0.6.2-1ubuntu1.1
---
gparted (0.6.2-1ubuntu1.1) maverick-proposed; urgency=low
* debian/patches/04_remove-misuse-of-ustring-in-get_filesystem.patch:
Apply patch from Seth Heeren to fix crash at startup (lp: #617885).
-- Michael
See https://help.ubuntu.com/community/UbuntuBackports for how to request
a backport of gparted 0.7.0-1 from natty to maverick-backports.
--
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/bugs/617885
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags added: verification-done
** Tags removed: verification-needed
--
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/bugs/617885
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Tested, it works now for me. Thanks!
--
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/bugs/617885
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Tested also, works for me.
--
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/bugs/617885
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Is this an x86-only build? It has yet to show up in Synaptic under PowerPC,
though many other packages *are* available from maverick-proposed.
The .deb mentioned above in comments #57 and #59 is still available, and still
dated November 4.
It's been made very clear that PowerPC is
The status of the gparted powerpc build is here:
https://launchpad.net/ubuntu/+source/gparted/0.6.2-1ubuntu1.1/+build/2060530
There's just a backlog, and the build will start in about 10 hours.
--
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/bugs/617885
You received this
The powerpc build is still pending as the powerpc buildds are currently
pretty loaded. It should hopefully build within the next days. You can
watch its status at
https://launchpad.net/ubuntu/+source/gparted/0.6.2-1ubuntu1.1/+build/2060530
The debs in maverick-proposed are different from those in
Thank you Brian, Michael -
Great to hear that PowerPC will be included. However a backport from Natty
would be preferable because one other critical fix is also included from
upstream, along with other bug fixes (quoted below from their release notes).
Is there a procedure for an end-user
Accepted gparted into maverick-proposed, the package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: gparted (Ubuntu
@jayseye: thanks for reporting that the existing deb works on Maverick
However, it didn't work on Lucid (1) which is the reason I created the
ppa. Perhaps other people are helped with that too.
Cheers,
Seth
(1) unresolvable missing dependencies
--
gparted crash at start: glibmm-ERROR **
I will sponsor this upload (and removed ubuntu-sponsors therefore).
** Changed in: gparted (Ubuntu Maverick)
Status: Triaged = In Progress
--
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/bugs/617885
You received this bug notification because you are a member of
** Description changed:
- Binary package hint: gparted
+ TEST CASE:
- Always that I try to open gparted from console:
+ 1. Start gparted from a terminal (starting from the menu works too):
+ 2. The gparted window appears and gparted is scanning the hard disks
+ 3. The gparted window disappears
Per #38 I checked and realized I had some zeroed filesystems, did
mkfs.ext4 on them, and now gparted works.
--
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/bugs/617885
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
A last checkback: I may note that where Arenlor refers to #38, I had this
analyzed with steps to reproduce back in #13 (patch in #12 from september
29th...).
It pains me to see that the general public is still not helped with that. I can
only hint at the new package for 0.7.0 (god knows
gparted 0.7.0 is in Ubuntu natty (the current Ubuntu development
version). And the links from other comments point to debs from natty.
Comment #53 contains a ready patch for a possible Ubuntu maverick SRU
and it just awaits review and sponsoring from an Ubuntu core-dev. This
bug is listed on the
Barring build problems 0.7.0 should be available for Lucid/Maverick
users in a few minutes from my own ppa
The simplest way to add it is
sudo add-apt-repository ppa:bugs-sehe/gparted
[Note that 0.7.0 is officially deemed unstable with respect to ubuntu. I
venture that it is more useful to
On 11/21/2010 09:29 PM, Michael Bienia wrote:
gparted 0.7.0 is in Ubuntu natty (the current Ubuntu development
version). And the links from other comments point to debs from natty.
Comment #53 contains a ready patch for a possible Ubuntu maverick SRU
and it just awaits review and sponsoring
Michael, thanks for the explanation. Re Comment #59 I am using that .deb under
Maverick, based on your info in Comment #53 stating that Natty was equivalent
to Maverick at that time. The .deb installed and worked flawlessly.
Perhaps this info may also be useful to you, Seth. In any case,
Agreed, gparted did not work for me on the amd64 Maverick live cd until
I downloaded the gparted 0.7.0 .deb. This needs to get into Maverick
and if possible Maverick live cd as soon as possible. I usually carry
around the latest Ubuntu live cd to do rescue on any computer that needs
it, often
As a workaround, I can recommend LiveCD Parted Magic, distribution
focused to disk manipulation. Gparted is the main application on the
disk; it is ready to go distribution, it is easier to run gparted from
PartedMagic LiveCD than to install some DEB packages to broken Ubuntu.
I experienced this gparted failure with the 10.10 i386 live-cd. I could
work around it with the .deb in message number 58.
--
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/bugs/617885
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Just installed gparted_0.7.0-1_i386.deb from
http://launchpadlibrarian.net/58607123/gparted_0.7.0-1_i386.deb
That fixed my gparted 0.6.2 crashing problem at Ubuntu 10.10.
Thanks !
--
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/bugs/617885
You received this bug
Yes I can also confirm that the .deb which I mentioned above fixes the problem
on PowerPC. Here's a direct link:
https://launchpad.net/ubuntu/+source/gparted/0.7.0-1/+build/2030806/+files/gparted_0.7.0-1_powerpc.deb
It would be really great to see this version actually released and
Have yet to find a binary package available in the repositories, at least for
PowerPC. However, .deb builds may be downloaded through the source package
page, under the word Builds:
https://launchpad.net/ubuntu/+source/gparted/0.7.0-1
While these probably still need testing, they at least
** Also affects: gparted (Ubuntu Maverick)
Importance: Undecided
Status: New
** Changed in: gparted (Ubuntu Maverick)
Status: New = Triaged
** Changed in: gparted (Ubuntu Maverick)
Importance: Undecided = High
--
gparted crash at start: glibmm-ERROR **
Got this bug on scan of my flash drive. Without on that flash it's
working.
~$ LC_ALL=C sudo fdisk -l /dev/sdb
Disk /dev/sdb: 4022 MB, 4022337536 bytes
124 heads, 62 sectors/track, 1021 cylinders
Units = cylinders of 7688 * 512 = 3936256 bytes
Sector size (logical/physical): 512 bytes / 512
This bug was fixed in the package gparted - 0.7.0-1
---
gparted (0.7.0-1) unstable; urgency=high
* New upstream release
Fix gparted crash at start with glibmm-ERROR
Closes: 601818
LP: #609477, #617885
Fix crash moving more than one logical partition right
Here is a debdiff for a Ubuntu 10.10 SRU based on the patch from Seth.
Note to sponsors:
I've tested this debdiff with gparted in natty (which is currently the same as
in maverick) as I don't have a maverick installation to test it.
The fix for natty is to sync gparted 0.7.0 from Debian unstable
Had the same bug, and this thread helped point me in the right
direction. I'm not sure if my response is appropriate, as I'm sure more
than a handful of less technical users will find this thread (it's the
first few hits for 'gparted crash' search results.) If not, I apologize
in advance. I
@seth - Sorry for forgetting to answer:
I just meant that in case there are people who don't need your patch can
build and use gparted from source - while not having all the
functionality. I'm looking forward to see your patch integrated. Thank
you for your work.
--
gparted crash at start:
Another data point:
I was encountering this bug when using an Ubuntu 10.10 Live CD (on
multiple machines).
Using the beta version of the System Rescue CD, GParted works.
Seth, Curtis: thanks a lot!
--
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/bugs/617885
You received
I am still having this problem on Ubuntu 10.10 64.
gksu gparted
==
libparted : 2.3
==
glibmm-ERROR **:
unhandled exception (type std::exception) in signal handler:
what: basic_string::_S_create
aborting...
--
gparted crash at start: glibmm-ERROR **
Thanks go to Seth for providing a patch to resolve this problem.
The enhancements to address this bug report have been included upstream in
GParted 0.7.0
which was released on October 29, 2010.
--
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/bugs/617885
You received this
How long does it typically take for a new upstream version to be packaged for
Ubuntu?
Having the same problem on PowerPC under Maverick, and may build from source if
there will be more than a few days of lag time.
Thanks to all who have helped trace and fix this issue!
Regards,
jaysye
In follow up to comment #32, the patch by Seth will be included in the
upstream release of GParted 0.7.0 on October 29, 2010.
For anyone interested in testing GParted 0.7.0-beta1 prior to the release date,
this version is currently available on the beta version of the System Rescue CD:
I would like to report that gaprted is still broken on Ubuntu 10.10 both
amd64 and x86 (I have tested this on both architectures).
On both machines it dies during start up. Here goes mysterious result
form gparted:
$ gksu gparted
==
libparted : 2.3
==
@Seth
Yup seems so.
In meantime since I really needed it I was able to build 0.64 from
source. Runs without problems but ?d prefer to use the distro packaged
gparted. Seems the gparted in maverick was patched to death? ;)
--
gparted crash at start: glibmm-ERROR **
On 10/18/2010 04:25 PM, Mathieu Simon wrote:
@Seth
Yup seems so.
In meantime since I really needed it I was able to build 0.64 from
source. Runs without problems but ?d prefer to use the distro packaged
gparted. Seems the gparted in maverick was patched to death? ;)
I don't really know
about using a zeroed image to reproduce, see my comment #13 (#12) for
analysis.
Also note a fix has been contributed both here (patch attached) and
upstream (see
http://gparted.sehe.nl/?p=gparted.git;a=commitdiff;h=2190bcfba4b), so
analysis can be safely considered complete, IMHO
Do we need to
U10.10, i386
$ sudo gparted
==
libparted : 2.3
==
glibmm-ERROR **:
unhandled exception (type std::exception) in signal handler:
what: basic_string::_S_create
aborting...
$ dpkg -la | grep gparted
ii gparted 0.6.2-1ubuntu1
@Seth: So the question is actually if the fix can be brought into Ubuntu
repositories. Would be quite sensible for me because gparted seems
completely broken.
--
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/bugs/617885
You received this bug notification because you are a
@nh2: +1. I would say, for many intents and purposes, gparted appears to
be broken.
--
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/bugs/617885
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Present in Ubuntu 10.10
Here's how I triggered the bug.
Use the shred command to zero out a partition:
shred -vz -n 1 /dev/sda2
Running gparted then results in:
dlaroche...@sileo:~$ sudo gparted
==
libparted : 2.3
==
glibmm-ERROR **:
unhandled
As DavidL reported, my partition was zeroed out, and gparted also crashed.
Once I ran mkfs.ext3 on it, gparted ran correctly.
--
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/bugs/617885
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It is broken for me
--
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/bugs/617885
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I'm using maverick amd64 livecd final release and this is broken for me.
--
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/bugs/617885
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I've just runned an upgrade and it's still brolen for me.
On Mon, Oct 11, 2010 at 4:02 PM, Shaggy 617...@bugs.launchpad.net
wrote:
I'm using maverick amd64 livecd final release and this is broken for me.
--
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/bugs/617885
You
Still broken with Ubuntu 10.10 Final amd64. parted (on console) does not
crash.
--
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/bugs/617885
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Just to make sure: Is gparted in today's 10.10 release broken?
--
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/bugs/617885
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
For example the following line of code to detect LUKS encryption:
if ( Glib::ustring( magic1 ) == LUKS\xBA\xBE )
Yes. If I'm reading comment #12 correctly, Seth is saying that ustring
constructor is often unhappy when fed with raw-from-disk data (invalid
utf-8?). In particular, he wrote:
On 10/05/2010 10:52 AM, Luca Bruno wrote:
Seth, care to comment?
My opinion is that it may be safer to do a plain memcmp, but I suspect the
issue Seth was experiencing was just due to buf_btrfs being not
NUL-terminated.
The nul termination was in order.
The problem is with the
Thank you Luca and Seth for clarifying the problem for me.
If I understand this correctly, one of the best ways to avoid this
problem is to not use Glib::ustring when reading data directly from the
disk.
Luca,
I will investigate removing the Glib::ustring stuff from the
I have taken the time to review all usage of ustring in gparted
This resulted in a patch against master (30efae4), which I attach. This
patch can be cleanly cherry-picked onto the btrfs branch.
You can also get the resulting revisions from my git repo
git remote add --fetch sehe.nl
On 10/05/2010 05:40 PM, Curtis Gedak wrote:
Thank you Luca and Seth for clarifying the problem for me.
If I understand this correctly, one of the best ways to avoid this
problem is to not use Glib::ustring when reading data directly from the
disk.
Luca,
I will investigate removing the
Wow, that was fast! Thank you Seth.
I will look into applying these patches to master. I appreciate you
supplying the git commands for your git repo too. Though I use git
frequently I am by no means an expert with git.
--
gparted crash at start: glibmm-ERROR **
On 10/05/2010 06:09 PM, Curtis Gedak wrote:
Wow, that was fast! Thank you Seth.
It wasn't! Your question just crossed my post at launchpad
I spent all afternoon fiddling with the codebase and eclipse CDT.
Eclipse rocks big time, fyi. I might be dropping vim for c++ development
after all
Thanks again for the patch Seth. My preliminary testing went well so I
have committed the patch to the Gnome git repository for GParted for
inclusion in the next release of GParted (0.7.0).
For those curious, the plans for GParted 0.7.0 can be viewed at the following
link:
Are you going to replace all those ustring objects for next release
cycle?
To clarify, are you referring to all of the ustring objects in the
GParted_Core::get_filesystems() method?
For example the following line of code to detect LUKS encryption:
if ( Glib::ustring( magic1 )
Thanks Seth for drawing my attention on this.
Firstly, I was not aware of this ubuntu patching, and I would suggest to
refresh the patch with the lucab/btrfs branch, which is currently much
healthier :)
Regarding the buf/buf_btrfs issue, it's certainly my fault and it slopped
through when
On 10/03/2010 05:23 PM, Luca Bruno wrote:
Thanks Seth for drawing my attention on this.
Firstly, I was not aware of this ubuntu patching, and I would suggest to
refresh the patch with the lucab/btrfs branch, which is currently much
healthier :)
Regarding the buf/buf_btrfs issue, it's
Thanks Seth for doing the hard work of finding the root cause of the
problem and for developing a patch to resolve the problem.
Also thank you Luca Bruno for subscribing me to this bug report.
I think that this problem is the same as the bug #609477:
gpartedbin crashed with signal 5 in
I think that this problem is the same as the bug #609477:
I think it too.
Are you going to replace all those ustring objects for next release cycle?
For GParted 0.7.0, we (upstream) plan to include BTRFS support, so the
patches from Seth are very timely. :-)
Curtis, as the discovery part is
This bug seems to be fixed (at least on my machine) in the HEAD revision
from git repo as well as source available at sourceforge.net (0.6.4).
--
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/bugs/617885
You received this bug notification because you are a member of Ubuntu
** Tags added: patch
--
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/bugs/617885
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
@Aurimas: I'd like to verify that but I don't know what repo you refer
to
Did you mean upstream (sf.net)? In that case, how would you know it is
fixed for ubuntu since the current problem lives exactly in the debian
patches (i.e. _not_ in upstream)?
If you have simply taken the latest from the
For background, I have just analysed the history in the git.gnome.org repo I
mention. There hasn't been a change recently there, a.f.a.i.c.t. More
specifically, their BTRFS detection code has been in there since Feb 23, 2009
(!!!) unaltered. So that makes it a part of upstream ever since
@Seth: Yes, I did mean git://git.gnome.org/gparted
My apologies for the noobness. I was not aware there were ubuntu
specific patches applied to the packages. Live and learn.
Your patch did prevent gparted from crashing on my setup.
--
gparted crash at start: glibmm-ERROR **
On 10/03/2010 12:32 AM, Aurimas wrote:
@Seth: Yes, I did mean git://git.gnome.org/gparted
My apologies for the noobness. I was not aware there were ubuntu
specific patches applied to the packages. Live and learn.
I'm pretty much the noob myself :)
Your patch did prevent gparted from
debian/patches/02-btrfs.patch is to blame, attaching a fix that works
for me.
Disabling it (by removing the patch or passing --disable-btrfs to configure)
might also remove the problem.
Attaching steps to reproduce in next post.
CODE ANALYSIS
==
GParted_Core.cc contains a glaring in
Steps to reproduce as promised
Using sparse loop devices on /tmp for brevity.
** Attachment added: steps to reproduce on maverick dd. sep 29, 2010
https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/617885/+attachment/1654737/+files/gparted.txt
--
gparted crash at start: glibmm-ERROR **
Arg my ubuntu/debian noobness is catching me out.
For some reason including the patch to the file mentioned does not work as
advertised. So instead, I went and modified the source manually, after which a
pdebuild generates a new patch file
debian/patches/debian-changes-0.6.2-1ubuntu1
I have the same problem with the last version available in the
repositories.
$ apt-cache policy gparted
gparted:
Instalados: 0.6.2-1ubuntu1
Candidato: 0.6.2-1ubuntu1
Tabla de versión:
*** 0.6.2-1ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages
I had the same problem but cannot reproduce it now since rebooting. I
don't recall changing anything. Gparted works fine now!
apt-cache policy gparted
gparted:
Installed: 0.6.2-1ubuntu1
Candidate: 0.6.2-1ubuntu1
Version table:
*** 0.6.2-1ubuntu1 0
500
On 09/15/2010 07:06 AM, Jan Claeys wrote:
$ ls -l /usr/bin/gksudo
lrwxrwxrwx 1 root root 4 2010-03-19 10:02 /usr/bin/gksudo - gksu*
So, gksu gksudo are the same application... ;)
I won't be surprised if this were related to e.g. bug #609447 and maybe
other threading bugs for
I still have this on maverick beta fresh install of today. How come?
I must admit I cannot use gksu, because it will never accept my password
(other bug?...) but sudo has always worked and it will be hard to
explain to users why it doesn't and they need to type other cryptic
characters instead of
Attaching a trace.
This is not related to sudo. I get the exact same trace when using
gksu[1].
It seems that it might be crashing while recognizing filesystems during disk
scan.
The crash is in GParted::GParted_Core::get_filesystem.
I get the crash with the following root-on lvm2 situation
Disregard my comments about gksu. I was confusing gksu and gksudo
--
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/bugs/617885
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
$ ls -l /usr/bin/gksudo
lrwxrwxrwx 1 root root 4 2010-03-19 10:02 /usr/bin/gksudo - gksu*
So, gksu gksudo are the same application... ;)
I won't be surprised if this were related to e.g. bug #609447 and maybe
other threading bugs for applications that use GObject.
--
gparted crash at
Yes, I can execute all times the gparted using gksu:
$ gksu gparted
==
libparted : 2.3
==
$ gksu gparted
==
libparted : 2.3
==
$ gksu gparted
==
libparted : 2.3
==
$ gksu
@Lito: Could you please check if this bug is really gone for you? I
could start up gparted successfully one time, but any other time I get:
ubu...@ubuntu:~$ gksu gparted
==
libparted : 2.3
==
glibmm-ERROR **:
unhandled exception (type std::exception) in
Now gparted start correctly:
$ apt-cache policy gparted
gparted:
Instalado: 0.6.0-1ubuntu1
Candidato: 0.6.0-1ubuntu1
Táboa de versións:
*** 0.6.0-1ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ maverick/main i386 Packages
100 /var/lib/dpkg/status
Thanks!
** Changed in:
When opening programs with root privileges you should use gksu. Do 'gksu
gparted' and see if this bug is still there.
--
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/bugs/617885
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
88 matches
Mail list logo
