nautilus crashed with SIGSEGV in g_object_set()

Bug #728978 reported by David Planella
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: nautilus

I opened Nautilus, then opened some text documents from a folder, and Nautilus crashed

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: nautilus 1:2.32.2.1-0ubuntu8
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CrashCounter: 1
Date: Fri Mar 4 11:21:15 2011
ExecutablePath: /usr/bin/nautilus
ProcCmdline: nautilus
ProcEnviron:
 LANGUAGE=ca_ES@valencia:ca:en_GB:en
 LANG=ca_ES.UTF-8
 LC_MESSAGES=ca_ES.utf8@valencia
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x354a9e <g_object_set+30>: mov (%esi),%eax
 PC (0x00354a9e) ok
 source "(%esi)" (0x64656727) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_object_set (_object=0x64656727, first_property_name=0x3f7f15b "show-local") at /build/buildd/glib2.0-2.28.1/./gobject/gobject.c:1816
 ?? () from /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so
 ?? () from /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so
 g_simple_async_result_complete (simple=0xa436568) at /build/buildd/glib2.0-2.28.1/./gio/gsimpleasyncresult.c:747
 reply_cb (connection=0x9edd1a0, res=0xa4365a0, user_data=0xa436568) at /build/buildd/glib2.0-2.28.1/./gio/gdbusproxy.c:2158
Title: nautilus crashed with SIGSEGV in g_object_set()
UpgradeStatus: Upgraded to natty on 2011-02-09 (22 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
David Planella (dpm) wrote :
Revision history for this message
David Planella (dpm) wrote :
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.