nautilus crashed with SIGSEGV

Bug #1067789 reported by Fungus
122
This bug affects 12 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I was unable to copy/cut/rename files or directories. Then nautilus crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
NonfreeKernelModules: fglrx wl
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Wed Oct 17 17:23:52 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+262+124'"
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'213'
 b'org.gnome.nautilus.window-state' b'start-with-status-bar' b'true'
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcCmdline: nautilus -n
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f458eddd8b3: mov 0x30(%rbx),%rdi
 PC (0x7f458eddd8b3) ok
 source "0x30(%rbx)" (0x0004b8e3) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: nautilus crashed with SIGSEGV
UpgradeStatus: Upgraded to quantal on 2012-10-10 (7 days ago)
UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo

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

StacktraceTop:
 free_node (node=node@entry=0x2e2f010) at /build/buildd/gtk+3.0-3.6.0/./gtk/gtkuimanager.c:1400
 update_node (manager=manager@entry=0x1912f20, node=0x2e2f010, in_popup=in_popup@entry=0, popup_accels=popup_accels@entry=0) at /build/buildd/gtk+3.0-3.6.0/./gtk/gtkuimanager.c:3118
 update_node (manager=manager@entry=0x1912f20, node=0x1939ca0, in_popup=in_popup@entry=0, popup_accels=popup_accels@entry=0) at /build/buildd/gtk+3.0-3.6.0/./gtk/gtkuimanager.c:3096
 update_node (manager=manager@entry=0x1912f20, node=0x1937980, in_popup=in_popup@entry=0, popup_accels=popup_accels@entry=0) at /build/buildd/gtk+3.0-3.6.0/./gtk/gtkuimanager.c:3096
 update_node (manager=manager@entry=0x1912f20, node=0x1987070, in_popup=in_popup@entry=0, popup_accels=popup_accels@entry=0) at /build/buildd/gtk+3.0-3.6.0/./gtk/gtkuimanager.c:3096

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
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
information type: Private → Public
Revision history for this message
terakin (terakinizers) wrote :

Maybe same bug (nautilus crash when copying & pasting a folder) is happening on my Ubuntu 12.04 LTS (amd64). I could not paste apport report just now, and I will report clearly when crash report is ready.

tags: added: bugpattern-needed
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.

Other bug subscribers

Remote bug watches

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