nautilus crashed with SIGSEGV in g_slice_free1()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
crashy-crashy
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nautilus 1:3.8.2-0ubuntu1
ProcVersionSign
Uname: Linux 3.11.0-9-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Wed Oct 2 20:18:39 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
b'org.
b'org.
MarkForUpload: True
ProcCmdline: nautilus -n
ProcEnviron:
LANGUAGE=en_GB
PATH=(custom, user)
XDG_RUNTIME_
LANG=en_GB.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f0f8e77c2f5: mov 0x8(%rdx),%rax
PC (0x7f0f8e77c2f5) ok
source "0x8(%rdx)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
?? () from /lib/x86_
?? () from /lib/x86_
g_slice_free1 () from /lib/x86_
g_type_
?? () from /usr/lib/
Title: nautilus crashed with SIGSEGV in g_slice_free1()
UpgradeStatus: Upgraded to saucy on 2013-09-17 (15 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare staff
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1196063, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.