nautilus crashed with SIGSEGV (copying data over USB)

Bug #713615 reported by Duncan Lithgow
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: nautilus

Copying large amount of data (24GB over about 40,000 files) from ATA HDD to external USB HDD. Crashed suddenly when I tried to burn a CD - happened twice so I guess that's what triggered the crash. The CD operation also vanished. Otherwise this looks similar to bug #203191 and bug #188105.

Update: This has just happened again with only the CD operation active - so it must be that which is causing the problem. It happens like this:
* I put in the DVD+RW (not blank)
* I accept the offer to open the default CD/DVD creator
* Add the CD image I want to burn (Ubuntu 10.10 64bit)
* Accept the offer to burn contents instead of file
* Crrrash

Important to note that this was only picked up the first time it happened. Now I can reproduce this crash at will and apport doesn't see a problem. Because this crash seems to be produced by th CD/DVD creator I have used ubuntu-bug to file a bug against brasero (is that the right application?) that bug is #713633

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: nautilus 1:2.32.0-0ubuntu1.3
ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
Uname: Linux 2.6.35-25-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CrashCounter: 1
Date: Sat Feb 5 12:51:46 2011
Disassembly: => 0x20bb012: Cannot access memory at address 0x20bb012
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
ProcCmdline: nautilus --sm-client-id 109b9f9886888fc9d2128049727579699600000011980036 --sm-client-state-file /home/username/.config/session-state/nautilus-1296899215.desktop
ProcEnviron:
 PATH=(custom, user)
 LANG=en_DK.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x20bb012: Cannot access memory at address 0x20bb012
 PC (0x020bb012) ok
 SP (0xbfe6b560) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1678): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (tracker-miner-fs:1648): Tracker-CRITICAL **: Could not execute sparql: Unable to insert multiple values for subject `urn:software-category:%2Fusr%2Fshare%2Fdesktop-directories%2Fwine-Programs-Accessories.directory' and single valued property `nfo:fileLastModified' (old_value: '<untransformable>', new value: '<untransformable>')
 (tracker-miner-fs:1648): Tracker-CRITICAL **: Could not execute sparql: Unable to insert multiple values for subject `urn:software-category:%2Fusr%2Fshare%2Fdesktop-directories%2Fwine-Programs.directory' and single valued property `nfo:fileLastModified' (old_value: '<untransformable>', new value: '<untransformable>')
 (tracker-miner-fs:1648): Tracker-CRITICAL **: Could not execute sparql: Unable to insert multiple values for subject `urn:software-category:%2Fusr%2Fshare%2Fdesktop-directories%2Fwine-wine.directory' and single valued property `nfo:fileLastModified' (old_value: '<untransformable>', new value: '<untransformable>')
 (tracker-miner-fs:1648): Tracker-CRITICAL **: Could not set mount point in database 'urn:nepomuk:datasource:c3491a67-4c06-4bab-8bc7-56d1d0164b11', Unable to insert multiple values for subject `urn:nepomuk:datasource:c3491a67-4c06-4bab-8bc7-56d1d0164b11' and single valued property `tracker:mountPoint' (old_value: '2134', new value: '221153')

Revision history for this message
Duncan Lithgow (duncan-lithgow) wrote :
Revision history for this message
Duncan Lithgow (duncan-lithgow) wrote :

This bug was automatically marked as private - please mark this as private if you feel that is safe - I can't tell.

description: updated
Revision history for this message
Duncan Lithgow (duncan-lithgow) wrote :

I mean mark as public if you feel that is okay - sorry.

description: updated
description: updated
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x020bb012 in ?? ()
 No symbol table info available.
 #1 0x005a80ea in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceTop:
 ?? ()
 ?? ()

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 an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libpango1.0-common: installed version 1.28.1-1ubuntu3, latest version: 1.28.2-0ubuntu1
libpango1.0-0: installed version 1.28.1-1ubuntu3, latest version: 1.28.2-0ubuntu1
libglib2.0-0: installed version 2.26.0-0ubuntu1, latest version: 2.26.1-0ubuntu1
libglib2.0-data: installed version 2.26.0-0ubuntu1, latest version: 2.26.1-0ubuntu1
libblkid1: installed version 2.17.2-0ubuntu1.10.10.1, latest version: 2.17.2-0ubuntu1.10.10.2
libuuid1: installed version 2.17.2-0ubuntu1.10.10.1, latest version: 2.17.2-0ubuntu1.10.10.2
util-linux: installed version 2.17.2-0ubuntu1.10.10.1, latest version: 2.17.2-0ubuntu1.10.10.2
mount: installed version 2.17.2-0ubuntu1.10.10.1, latest version: 2.17.2-0ubuntu1.10.10.2

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-i386-retrace
visibility: private → public
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.