nautilus crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
Binary package hint: nautilus
crash... stack contains ?? but I suspect after retracing it might become a dupe of Bug #403549 ??
ProblemType: Crash
Architecture: amd64
Date: Sat Jan 30 15:45:01 2010
Disassembly: 0x7f5667bf8def: Cannot access memory at address 0x7f5667bf8def
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.29.2-0ubuntu1
ProcCmdline: nautilus --sm-client-id 1047cea494f3871
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x7f5667bf8def: Cannot access memory at address 0x7f5667bf8def
PC (0x7f5667bf8def) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()
Title: nautilus crashed with SIGSEGV
Uname: Linux 2.6.32-12-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
apport crash report was there in notification tray pretty much right away when I booted it... I'm using lucid pre-release bits as of 2010-01-30... the crash doesn't happen every boot