nautilus crashed with SIGSEGV in g_slice_free1()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Nautilus crashed on close.
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: nautilus 1:3.14.2-0ubuntu4
ProcVersionSign
Uname: Linux 3.19.0-9-generic x86_64
NonfreeKernelMo
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Mar 22 22:54:34 2015
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.
InstallationDate: Installed on 2015-01-09 (71 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
ProcCmdline: nautilus -n
SegvAnalysis:
Segfault happened at: 0x7fdfff61a804: movq $0x0,0x8(%rcx)
PC (0x7fdfff61a804) ok
source "$0x0" ok
destination "0x8(%rcx)" (0x00000008) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
?? () from /lib/x86_
?? () from /lib/x86_
g_slice_free1 () from /lib/x86_
?? () from /lib/x86_
g_variant_unref () from /lib/x86_
Title: nautilus crashed with SIGSEGV in g_slice_free1()
UpgradeStatus: Upgraded to vivid on 2015-02-28 (22 days ago)
UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
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 #1424204, 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.