nautilus crashed with SIGSEGV in exit()

Bug #439240 reported by Marcin
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: nautilus

When I logged into the system, the report was in the systray
Ubuntu 9.10 amd64
nautilus 2.28.0-0ubuntu3

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 29 15:32:54 2009
Disassembly: 0x7fb5d21635f0: Cannot access memory at address 0x7fb5d21635f0
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: nautilus 1:2.28.0-0ubuntu3
ProcCmdline: nautilus
ProcEnviron:
 PATH=(custom, user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SegvAnalysis:
 Segfault happened at: 0x7fb5d21635f0: Cannot access memory at address 0x7fb5d21635f0
 PC (0x7fb5d21635f0) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 exit () from /lib/libc.so.6
 __libc_start_main () from /lib/libc.so.6
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in exit()
Uname: Linux 2.6.31-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare scanner
usr_lib_nautilus:
 nautilus-actions 1.10.1-1
 libbrasero-media0 2.28.0-0ubuntu1
 evince 2.28.0-0ubuntu1
 file-roller 2.28.0-0ubuntu1
 gksu 2.0.2-2ubuntu1

Revision history for this message
Marcin (marcinsud) wrote :
Marcin (marcinsud)
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.