nautilus crashed with SIGSEGV

Bug #1250257 reported by Stephen Early
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Just finished copying a file to a USB stick, which was then unmounted. The "Eject" button was pressed before the copy finished; a window popped up saying the volume was still busy. When the copy finished the "busy" window disappeared, a notification saying not to remove the volume until the write finished appeared, and then nautilus crashed.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nautilus 1:3.8.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Mon Nov 11 23:51:01 2013
Disassembly: => 0x7ff67e91d2ef: Cannot access memory at address 0x7ff67e91d2ef
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'geometry' b"'1284x815+287+24'"
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'167'
InstallationDate: Installed on 2011-10-17 (756 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MarkForUpload: True
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ff67e91d2ef: Cannot access memory at address 0x7ff67e91d2ef
 PC (0x7ff67e91d2ef) ok
 SP (0x7fffdd964380) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV
UpgradeStatus: Upgraded to saucy on 2013-10-17 (25 days ago)
UserGroups: adm admin cdrom dialout libvirtd lp lpadmin plugdev sambashare

Revision history for this message
Stephen Early (steve-greenend) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

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):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for libindicator3-7: package version 12.10.2+13.10.20130913-0ubuntu2 dbgsym version 12.10.2+13.10.20130913-0ubuntu1
outdated debug symbol package for libudev1: package version 204-0ubuntu19 dbgsym version 204-0ubuntu18
outdated debug symbol package for libavformat53: package version 6:0.8.9-0ubuntu0.13.10.1 dbgsym version 6:0.8.9-0ubuntu0.13.04.1
outdated debug symbol package for libavutil51: package version 6:0.8.9-0ubuntu0.13.10.1 dbgsym version 6:0.8.9-0ubuntu0.13.04.1
outdated debug symbol package for libunity9: package version 7.1.2+13.10.20131010-0ubuntu2 dbgsym version 7.1.2+13.10.20131010-0ubuntu1
outdated debug symbol package for file-roller: package version 3.10.1-0ubuntu1 dbgsym version 3.10.0-0ubuntu1
outdated debug symbol package for libavcodec53: package version 6:0.8.9-0ubuntu0.13.10.1 dbgsym version 6:0.8.9-0ubuntu0.13.04.1
outdated debug symbol package for libunity-protocol-private0: package version 7.1.2+13.10.20131010-0ubuntu2 dbgsym version 7.1.2+13.10.20131010-0ubuntu1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
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.