nautilus crashed with SIGSEGV in g_type_check_instance()

Bug #1201889 reported by Marco Giannini
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

crash when i rename a file

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nautilus 1:3.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
Uname: Linux 3.10.0-3-generic i686
ApportVersion: 2.10.2-0ubuntu4
Architecture: i386
Date: Tue Jul 16 18:56:33 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'840x550+57+24'"
InstallationDate: Installed on 2013-07-08 (8 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130707)
MarkForUpload: True
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=it
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb6b07621 <g_type_check_instance+33>: mov (%eax),%edx
 PC (0xb6b07621) ok
 source "(%eax)" (0x00000020) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_type_check_instance () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_signal_connect_data () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in g_type_check_instance()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Marco Giannini (marco-giannini) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance (type_instance=type_instance@entry=0xa85eb38) at /build/buildd/glib2.0-2.37.3/./gobject/gtype.c:4082
 g_signal_connect_data (instance=0xa85eb38, detailed_signal=detailed_signal@entry=0x814f84e "destroy", c_handler=c_handler@entry=0x80d0620 <pending_icon_to_reveal_destroy_callback>, data=data@entry=0xa15d478, destroy_data=destroy_data@entry=0x0, connect_flags=connect_flags@entry=(unknown: 0)) at /build/buildd/glib2.0-2.37.3/./gobject/gsignal.c:2435
 set_pending_icon_to_reveal (container=container@entry=0xa15d478, icon=icon@entry=0xa31dfd0) at nautilus-canvas-container.c:592
 end_renaming_mode (container=container@entry=0xa15d478, commit=commit@entry=1) at nautilus-canvas-container.c:7454
 icon_toggle_selected (container=0xa15d478, icon=icon@entry=0xa31dfd0) at nautilus-canvas-container.c:442

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 nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
tags: added: trusty
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nautilus (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

The bug didn't get activity/new duplicates for some years and the nautilus code saw quite some changes since which probably deprecated the issue so closing it. If it's still a problem in recent Ubuntu/nautilus version please submit a new report

Changed in nautilus (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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