gedit crashed with SIGSEGV in g_type_check_instance_is_a()

Bug #813653 reported by ubername
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GTK+
Invalid
Critical
gtk+3.0 (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

trying to open a second file in gedit
on a Flaky oneiric install

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gedit 3.1.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
Uname: Linux 3.0.0-5-generic x86_64
Architecture: amd64
Date: Wed Jul 20 18:33:05 2011
ExecutablePath: /usr/bin/gedit
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110417)
ProcCmdline: gedit
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fa91b173ff0 <g_type_check_instance_is_a+112>: testb $0x4,0x16(%rdi)
 PC (0x7fa91b173ff0) ok
 source "$0x4" ok
 destination "0x16(%rdi)" (0x7fa900100016) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gedit
StacktraceTop:
 g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_file_equal () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/libgtk-3.so.0
 ?? () from /usr/lib/libgtk-3.so.0
 ?? () from /usr/lib/libgtk-3.so.0
Title: gedit crashed with SIGSEGV in g_type_check_instance_is_a()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

Revision history for this message
ubername (ubername) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance_is_a (type_instance=<value optimized out>, iface_type=<value optimized out>) at /build/buildd/glib2.0-2.29.10/./gobject/gtype.c:3952
 g_file_equal (file1=0x2b76c60, file2=0x2b97240) at /build/buildd/glib2.0-2.29.10/./gio/gfile.c:585
 gtk_path_bar_check_parent_path (path_bar=0x2570460, file=0x2b76c60, keep_trail=<value optimized out>, error=<value optimized out>) at /build/buildd/gtk+3.0-3.1.8/./gtk/gtkpathbar.c:1581
 _gtk_path_bar_set_file (path_bar=0x2570460, file=0x2b76c60, keep_trail=<value optimized out>, error=<value optimized out>) at /build/buildd/gtk+3.0-3.1.8/./gtk/gtkpathbar.c:1754
 update_current_folder_get_info_cb (cancellable=0x2b49ef0, info=<value optimized out>, error=<value optimized out>, user_data=0x2c12a00) at /build/buildd/gtk+3.0-3.1.8/./gtk/gtkfilechooserdefault.c:7095

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gedit (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :
affects: gedit (Ubuntu) → gtk+3.0 (Ubuntu)
Changed in gtk+3.0 (Ubuntu):
status: New → Incomplete
status: Incomplete → Triaged
Changed in gtk:
importance: Unknown → Critical
status: Unknown → New
Changed in gtk:
status: New → Invalid
Revision history for this message
Lars Karlitski (larsu) wrote :

This was fixed upstream: https://bugzilla.gnome.org/show_bug.cgi?id=664137

The upstream bug linked here is a duplicate of the above.

Changed in gtk+3.0 (Ubuntu):
status: Triaged → Fix Released
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.