nautilus crashed with SIGSEGV in __libc_start_main()

Bug #542359 reported by Mike Basinger
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: nautilus

Nautilus will not start after doing upgrades in Lucid on 19-March-2010.

ProblemType: Crash
Architecture: i386
Date: Fri Mar 19 19:41:06 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
NonfreeKernelModules: nvidia
Package: nautilus 1:2.29.92.1-0ubuntu2
ProcCmdline: nautilus
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
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: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Mike Basinger (mike.basinger) 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.