nautilus crashed with SIGSEGV

Bug #1223151 reported by Phil Wyett
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Scenario:

  - On second HDD, right click in nautilus and create a link to a folder.
  - Right click and move link to HOME on primary HDD.
  - Delete folder in HOME i.e. 'Music'.
  - Rename link to Music and hit RETURN.

Note: This may cause failure working off same HDD, but this is what I do to reproduce at this time.

Result:

  - nautiuls will crash.

What should happen:

  - nauitlus should not crash and rename should complete without error.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nautilus 1:3.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
Uname: Linux 3.11.0-5-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Tue Sep 10 04:11:52 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'202'
InstallationDate: Installed on 2013-09-09 (0 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: nautilus --new-window
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x4bc90b: cmp %rax,(%rdx)
 PC (0x004bc90b) ok
 source "%rax" ok
 destination "(%rdx)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV
UpgradeStatus: Upgraded to saucy on 2013-09-09 (0 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
Phil Wyett (u-k-i-t) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 nautilus_file_get_uri (file=0x1188f90) at nautilus-file.c:1602
 get_link_files (target_file=target_file@entry=0x1188f90) at nautilus-file.c:2098
 nautilus_file_emit_changed (file=0x1188f90) at nautilus-file.c:7205
 nautilus_directory_emit_change_signals (directory=0x7f276800f6a0, changed_files=changed_files@entry=0x7fff47f105c0) at nautilus-directory.c:820
 nautilus_file_changed (file=0x1188f90) at nautilus-file.c:7157

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
Ads20000 (ads20000) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 1223151

and any other logs that are relevant for this particular issue.

Changed in nautilus (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]

Changed in nautilus (Ubuntu):
status: Incomplete → Expired
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.