Vivid Beta 2
Mouse cursor move a document from desktop to Documents folder got this failure.
DISTRIB_RELEASE=15.04
DISTRIB_CODENAME=vivid
DISTRIB_DESCRIPTION="Ubuntu Vivid Vervet (development branch)"
Linux Lenovo2 3.19.0-10-generic #10-Ubuntu SMP Mon Mar 23 16:25:20 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: nautilus 1:3.14.2-0ubuntu6
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic x86_64
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Mar 27 22:36:19 2015
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
InstallationDate: Installed on 2015-03-26 (1 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
ProcCmdline: nautilus -n
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f06ef834fa3: mov (%rax),%rax
PC (0x7f06ef834fa3) ok
source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: nautilus crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 reached EOL
See this document for currently supported Ubuntu releases: https:/
I've tried recreating this bug and was unable to, given the information you've provided. Please upgrade to the latest version and re-test. If the bug is still reproducible, increase the verbosity of the steps to recreate it so we can try again.
Do feel free to report any other bugs you may find.