nautilus crashed with SIGSEGV in build_file_list_from_uris()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Nautilus |
Fix Released
|
Medium
|
|||
gtk+3.0 (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Wily |
Fix Released
|
High
|
Unassigned |
Bug Description
I was trying to copy a file out of a VMware Player virtual Windows 7 guest runnning in a window to nautilus, drag-and-dropping. The reverse operation (From nautilus to virtual machine's desktop) is executed fine.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: nautilus 1:3.10.1-0ubuntu4
ProcVersionSign
Uname: Linux 3.13.0-11-generic x86_64
NonfreeKernelMo
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Feb 22 13:16:46 2014
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
InstallationDate: Installed on 2014-02-15 (7 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140214)
ProcCmdline: nautilus -n
SegvAnalysis:
Segfault happened at: 0x7f36910aa0b9: mov (%rdi),%rdi
PC (0x7f36910aa0b9) ok
source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
Title: nautilus crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
Related branches
Changed in nautilus: | |
importance: | Unknown → Medium |
status: | Unknown → Confirmed |
affects: | nautilus (Ubuntu) → gtk+3.0 (Ubuntu) |
Changed in gtk+3.0 (Ubuntu): | |
status: | Triaged → Fix Committed |
Changed in nautilus: | |
status: | Confirmed → Invalid |
Changed in nautilus: | |
importance: | Medium → Unknown |
status: | Invalid → Unknown |
Changed in nautilus: | |
importance: | Unknown → Medium |
status: | Unknown → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.