The bug didn't get activity/new duplicates for some years and the
nautilus code saw quite some changes since which probably deprecated the
issue so closing it. If it's still a problem in recent Ubuntu/nautilus
version please submit a new report
** Changed in: nautilus (Ubuntu)
Status: Confi
pratically all dbgsym installed
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1158735
Title:
nautilus crash
SegvAnalysis:
Segfault happened at: 0x7fb4c000c711 <__strlen_sse2_pminub+17>:movdqu
(%rdi),%xmm1
PC (0x7fb4c000c711) ok
source "(%rdi)" (0x3fe0) not located in a known VMA region (needed
readable region)!
destination "%xmm1" ok
SegvReason: reading unknown VMA
SourcePackage
** Changed in: nautilus (Ubuntu)
Status: New => Confirmed
** Tags added: saucy
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1158735
Title:
nautilus crashed with SIGSEGV
Thank you for your bug report, could be an issue with the new GTK from
the ppa, it doesn't seem we are getting reports from raring
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1158
