[Oneiric] Nautilus crashes with SIGSEGV on each and every boot

Bug #805678 reported by VinDSL
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I have been getting this error message on every boot, for a couple of weeks.

It doesn't cause any major problems - more of an irritation, than anything.

I assumed that sooner-or-later, this-or-that Daily Build or Synaptic Update would take care of the situation, but the error just keeps popping up, on each and every boot, e.g. easily reproducible.

Thus, I thought I should take the time to report it...

Here are some particulars, of my install:

* UbuOO 22-Jun Daily Build - fully patched & mod'ed
* 4-Jul Mainline Kernel

$ date && lsb_release -sd || cat /etc/*release && uname -s -r && unity --version && /usr/lib/nux/unity_support_test -p
Mon Jul 4 13:43:19 MST 2011
Ubuntu oneiric (development branch)
Linux 3.0.0-999-generic
unity 4.2.0
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce 7600 GT/AGP/SSE2
OpenGL version string: 2.1.2 NVIDIA 275.09.07

Not software rendered: yes
Not blacklisted: yes
GLX fbconfig: yes
GLX texture from pixmap: yes
GL npot or rect textures: yes
GL vertex program: yes
GL fragment program: yes
GL vertex buffer object: yes
GL framebuffer object: yes
GL version is 1.4+: yes

Unity supported: yes

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.3-0ubuntu1
Uname: Linux 3.0.0-999-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CrashCounter: 1
Date: Sat Jul 2 14:55:31 2011
Disassembly: => 0xb6a2f6fa: Cannot access memory at address 0xb6a2f6fa
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110623)
ProcCmdline: nautilus
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb6a2f6fa: Cannot access memory at address 0xb6a2f6fa
 PC (0xb6a2f6fa) ok
 Stack memory exhausted (SP below stack segment)
 SP (0xb150ee6c) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
VinDSL (perfect-pecker) wrote :
description: updated
description: updated
description: updated
VinDSL (perfect-pecker)
description: updated
visibility: private → public
summary: - nautilus crashed with SIGSEGV on each and every boot
+ nautilus crashes with SIGSEGV on each and every boot
VinDSL (perfect-pecker)
summary: - nautilus crashes with SIGSEGV on each and every boot
+ [Oneiric] nautilus crashes with SIGSEGV on each and every boot
summary: - [Oneiric] nautilus crashes with SIGSEGV on each and every boot
+ [Oneiric] Nautilus crashes with SIGSEGV on each and every boot
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 : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace.
Please try to obtain a backtrace manually following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in nautilus (Ubuntu):
importance: Undecided → Medium
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.