nautilus crashed with SIGSEGV in xmp_free()

Bug #1725242 reported by mlentink on 2017-10-20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)

Bug Description

Trying to delete items in Trash, probably caused by mounted Google drives through google-drive-ocamlfuse (gdfuse)

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 13:19:16 2017
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2017-10-17 (3 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
ProcCmdline: /usr/bin/nautilus --gapplication-service
 PATH=(custom, no user)
 Segfault happened at: 0x7fe121c665e2 <xmp_free+34>: mov (%rbx),%rax
 PC (0x7fe121c665e2) ok
 source "(%rbx)" (0x000021a0) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
 xmp_free () from /usr/lib/x86_64-linux-gnu/
 ?? ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
Title: nautilus crashed with SIGSEGV in xmp_free()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare sudo

mlentink (martin-athenenoctua) wrote :

 xmp_free (xmp=0x21a0) at exempi.cpp:646
 load_finished (page=page@entry=0x56230f07bd30) at ../src/nautilus-image-properties-page.c:503
 file_open_callback (object=<optimized out>, res=0x56230de78390, user_data=0x56230fef30d0) at ../src/nautilus-image-properties-page.c:669
 g_task_return_now (task=0x56230de78390) at ../../../../gio/gtask.c:1145
 g_task_return (task=0x56230de78390, type=<optimized out>) at ../../../../gio/gtask.c:1203

Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Changed in nautilus (Ubuntu):
importance: Medium → Low
information type: Private → Public
Paul White (paulw2u) wrote :

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.

Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

Do you still see a problem related to the one that you reported in a currently supported version of Ubuntu? Please let us know if you do and in which version of Ubuntu otherwise this report can be left to expire in approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

Changed in nautilus (Ubuntu):
status: New → Incomplete
mlentink (martin-athenenoctua) wrote :

Hi Paul,

and thanks for the heads-up. I'm on 18.10 currently and don't see his issue anymore, so I assumed it had been fixed in the meantime without bothering to check here. Sorry about that!


Changed in nautilus (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers