nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
1) The release of Ubuntu
$ lsb_release -rd
Description: Ubuntu 16.04.2 LTS
Release: 16.04
2) The version of the package
$ apt-cache policy nautilus
nautilus:
Installed: 1:3.18.
Candidate: 1:3.18.
Version table:
*** 1:3.18.
500 http://
100 /var/lib/
1:
500 http://
3) What I expected to happen
I expected nautilus to show me a file that was recently changed according to Dropbox.
4) What happened instead
Nautilus crashed and did not show me the file.
I tried to show a file that Dropbox recently synced. I have a Dropbox icon on xfce4-panel. I clicked on the Dropbox icon, clicked on an item in "Recently Changed Files" and nautilus supposedly tried to show me that file but crashed.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.
ProcVersionSign
Uname: Linux 4.4.0-78-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Jun 29 10:48:10 2017
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
b'org.
b'org.
InstallationDate: Installed on 2014-12-04 (937 days ago)
InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
ProcCmdline: nautilus --no-desktop --select /home/username/
SegvAnalysis:
Segfault happened at: 0x7f4ff3aec9f0: mov (%rdi),%rax
PC (0x7f4ff3aec9f0) ok
source "(%rdi)" (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/
?? () from /usr/lib/
?? ()
g_cclosure_
?? () from /usr/lib/
Title: nautilus crashed with SIGSEGV in g_cclosure_
UpgradeStatus: Upgraded to xenial on 2016-07-26 (337 days ago)
UserGroups: adm audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare scanner sudo video
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 #1506816, 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.