gparted segfault after applying change

Bug #150700 reported by gregwebs
4
Affects Status Importance Assigned to Milestone
gparted (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: gparted

second time (in a row) I got this bug after upgrading to Ubuntu Gusty.
after hitting apply, program crashes, but it successfully made the change.

ProblemType: Crash
Architecture: i386
Date: Mon Oct 8 15:29:20 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/gparted
Package: gparted 0.3.3-2ubuntu6
PackageArchitecture: i386
ProcCmdline: gparted
ProcCwd: /home/greg
ProcEnviron:
 SHELL=/usr/bin/zsh
 LANG=en_US.UTF-8
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
Signal: 11
SourcePackage: gparted
StacktraceTop:
 std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string () from /usr/lib/libstdc++.so.6
 Glib::ustring::ustring () from /usr/lib/libglibmm-2.4.so.1
 ?? ()
 ?? ()
 Glib::SignalProxyNormal::slot0_void_callback ()
Title: gparted crashed with SIGSEGV in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string()
Uname: Linux grubtop 2.6.22-13-generic #1 SMP Thu Oct 4 17:18:44 GMT 2007 i686 GNU/Linux
UserGroups:

Tags: apport-crash
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:ustring (this=0xbfad9c1c, other=@0x31) at ustring.cc:296
GParted::Device::get_path (this=0xb5704600) at Device.cc:62
GParted::Win_GParted::combo_devices_changed (this=0xbfadbf1c) at Win_GParted.cc:921
Glib::SignalProxyNormal::slot0_void_callback (self=0x816f030, data=0x81a8158) at /usr/include/sigc++-2.0/sigc++/functors/slot.h:440
IA__g_cclosure_marshal_VOID__VOID (closure=0x81a8448, return_value=0x0, n_param_values=1, param_values=0xbfad9e8c, invocation_hint=0xbfad9d9c,

Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in gparted:
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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