nautilus crashed with SIGSEGV

Bug #784974 reported by David Nielsen
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: nautilus

No idea what happened, apport caught random crash it seems

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.0.1.1-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.39-2.8-generic 2.6.39-rc7
Uname: Linux 2.6.39-2-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
Date: Thu May 19 06:01:08 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110409)
ProcCmdline: nautilus
ProcEnviron:
 LANGUAGE=da_DK:en
 PATH=(custom, no user)
 LANG=da_DK.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x486604: mov 0xb0(%rdi),%rax
 PC (0x00486604) ok
 source "0xb0(%rdi)" (0x000000b0) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
Stacktrace:
 #0 0x0000000000486604 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fff231cbc88
StacktraceTop: ?? ()
Title: nautilus crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
David Nielsen (davidnielsen-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 set_floating_bar_status (slot=0x1381410, status=<value optimized out>, short_status=0x0) at nautilus-window-slot.c:575
 nautilus_window_slot_set_status (slot=0x1381410, status=<value optimized out>, short_status=0x0) at nautilus-window-slot.c:594

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.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
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.

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.