Crashed twice, once when hitting 'Cancel' another when I hit undo

Bug #375095 reported by Ajay
40
This bug affects 9 people
Affects Status Importance Assigned to Milestone
GParted
Fix Released
Medium
gparted (Ubuntu)
Fix Released
Medium
Phillip Susi

Bug Description

Binary package hint: gparted

It crashed on me twice in a row, but before and after that it has been working fine.
I was using the 'Resize/Move' option, and had hit esc and/or cancel to get out of the dialog box, when it paused, then crashed.
The other time I was using the 'Undo' to undo pending operations, and it crashed during.
hth!

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/sbin/gpartedbin
MediaBuild: Ubuntu 9.04 "Jaunty Jackalope" - Release amd64 (20090420.1)
Package: gparted 0.4.3-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/sbin/gpartedbin
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gparted
StacktraceTop:
 ?? () from /lib/libc.so.6
 ?? ()
 Glib::SignalProxyNormal::slot0_void_callback ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: gpartedbin crashed with SIGSEGV in Glib::SignalProxyNormal::slot0_void_callback()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups:

Revision history for this message
Ajay (atallam) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:main_arena () from /lib/libc.so.6
GParted::Dialog_Base_Partition::on_spinbutton_value_changed (this=0x7fff88310c10, spinbutton=2284916176)
Glib::SignalProxyNormal::slot0_void_callback (
IA__g_closure_invoke (closure=0x19e8830,
signal_emit_unlocked_R (node=0x13396f0, detail=0,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in gparted (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Kees Cook (kees)
visibility: private → public
Revision history for this message
Helvecio (helv-wp) wrote :

I was using the LiveCD 32-bits when this error happened.

amithji (coolamith23)
Changed in gparted (Ubuntu):
status: New → Incomplete
status: Incomplete → New
Revision history for this message
Curtis Gedak (gedakc) wrote :

As shown in the upstream bug report, the crash problem when hitting the ESC key in the Resize/Move dialog window has been confirmed. So far I have been unable to confirm the crash when using the menu option "Edit --> Undo last operation" or the "Undo" toolbar button.

Changed in gparted:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
Phillip Susi (psusi) wrote :

This is almost certainly due to the use of pthread_cancel() in the cancelation pathway, which is fundamentally unsafe. I have some patches to refactor the code to remove this, but I have not had time to finish them lately.

Changed in gparted (Ubuntu):
status: New → Triaged
assignee: nobody → Phillip Susi (psusi)
Revision history for this message
Curtis Gedak (gedakc) wrote :

Phillip, I should have some more free time starting late November. If there is something I can help with then just let me know.

Revision history for this message
Curtis Gedak (gedakc) wrote :

Phillip, with regards to the refactoring to remove pthread, is there an upstream bug report that we should link to? If not then perhaps we should create one to help track the progress of the refactoring.

Revision history for this message
Phillip Susi (psusi) wrote :

You would be in a better position to know that than me ;)

Revision history for this message
Curtis Gedak (gedakc) wrote :

Phillip, I read through the list of upstream GParted patches and did not find one that exactly matched the refactoring issue. As such I have created the following upstream bug report:

Bug 685740 - Refactor to use asynchronous command execution
https://bugzilla.gnome.org/show_bug.cgi?id=685740

Changed in gparted:
status: Confirmed → Fix Released
Phillip Susi (psusi)
Changed in gparted (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.