nautilus crashed with SIGSEGV in __libc_start_main()

Bug #542444 reported by agitdd99
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: nautilus

got nautilus error in lucid per 20th March 2010 after updating.

ProblemType: Crash
Architecture: i386
Date: Sat Mar 20 13:34:20 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100314)
NonfreeKernelModules: nvidia
Package: nautilus 1:2.29.92.1-0ubuntu2
ProcCmdline: nautilus
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SegvAnalysis:
 Segfault happened at: 0x8161038: mov 0x8(%eax),%edx
 PC (0x08161038) ok
 source "0x8(%eax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
Title: nautilus crashed with SIGSEGV in __libc_start_main()
Uname: Linux 2.6.32-16-generic i686
UserGroups:

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