Ubuntu
gparted package

gparted crashed with SIGSEGV in Gtk::CheckMenuItem::set_active()

Bug #146315 reported by Dave roi on 2007-09-28

This bug report is a duplicate of: Bug #141516: [MASTER] Gparted crashes when refreshing devices. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	gparted (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: gparted

Tried to unmount /tmp (using gparted GUI)

ProblemType: Crash
Architecture: i386
Date: Fri Sep 28 16:08:29 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/gparted
NonfreeKernelModules: nvidia
Package: gparted 0.3.3-2ubuntu5
PackageArchitecture: i386
ProcCmdline: gparted
ProcCwd: /home/dave
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: gparted
StacktraceTop:
Gtk::CheckMenuItem::set_active ()
?? ()
Glib::SignalProxyNormal::slot0_void_callback ()
g_cclosure_marshal_VOID__VOID ()
g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
Title: gparted crashed with SIGSEGV in Gtk::CheckMenuItem::set_active()
Uname: Linux davebuntu 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux
UserGroups:

Tags:

Revision history for this message

Dave roi (daveroi) wrote on 2007-09-28:

Dependencies.txt Edit (5.3 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (18.3 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (593 bytes, text/plain; charset="utf-8")
Registers.txt Edit (522 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (478 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (506 bytes, text/plain; charset="utf-8")

Revision history for this message

Saivann Carignan (oxmosys) wrote on 2007-11-20:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 141516, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.