nautilus crashed with SIGSEGV

Bug #851742 reported by Jiří Podvolecký
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Medium
Unassigned

Bug Description

There is crush occured during finishing installing nvidia videodriver ( current ). I expect message about restart vice it.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.90-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Fri Sep 16 12:05:40 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110915)
ProcCmdline: nautilus -n
ProcEnviron:
 PATH=(custom, no user)
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x486804: mov 0xa8(%rdi),%rax
 PC (0x00486804) ok
 source "0xa8(%rdi)" (0x000000a8) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
Stacktrace:
 #0 0x0000000000486804 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fffb08a6c88
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
Jiří Podvolecký (jiripodvolecky) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 nautilus_window_slot_get_current_uri (slot=0x0) at nautilus-window-slot.c:648
         __PRETTY_FUNCTION__ = "nautilus_window_slot_get_current_uri"
 Cannot access memory at address 0x7fffb08a6c88
StacktraceTop: nautilus_window_slot_get_current_uri (slot=0x0) at nautilus-window-slot.c:648

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
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.