nautilus crashed with SIGSEGV in g_object_get_qdata()

Bug #672128 reported by Gary M
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: nautilus

Error was shown while changing current folder in nautilus with mouse double-clicks.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: nautilus 1:2.32.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-23.37-generic 2.6.35.7
Uname: Linux 2.6.35-23-generic i686
Architecture: i386
Date: Sun Nov 7 23:19:15 2010
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100803.1)
ProcCmdline: nautilus
ProcEnviron:
 LANG=en_NZ.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x6d4264 <g_object_get_qdata+36>: mov (%esi),%eax
 PC (0x006d4264) ok
 source "(%esi)" (0x0000000b) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_object_get_qdata (object=0xb, quark=1001) at /build/buildd/glib2.0-2.26.0/gobject/gobject.c:2727
 get_size_groups (widget=0xb, requisition=0xbfa7dac8) at /build/buildd/gtk+2.0-2.22.0/gtk/gtksizegroup.c:77
 _gtk_size_group_get_child_requisition (widget=0xb, requisition=0xbfa7dac8) at /build/buildd/gtk+2.0-2.22.0/gtk/gtksizegroup.c:784
 IA__gtk_widget_get_child_requisition (widget=0xb, requisition=0xbfa7dac8) at /build/buildd/gtk+2.0-2.22.0/gtk/gtkwidget.c:3938
 nautilus_path_bar_size_allocate (widget=0x8a0e800, allocation=0xbfa7de70) at nautilus-pathbar.c:670
Title: nautilus crashed with SIGSEGV in g_object_get_qdata()
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Gary M (garym) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

Changed in nautilus (Ubuntu):
importance: Undecided → Low
status: New → Invalid
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.