nautilus crashed with SIGSEGV in nautilus_progress_manager_has_viewers()

[GuiroZ]

Copying files

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 19 10:25:22 2017
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2015-10-06 (713 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
ProcCmdline: /usr/bin/nautilus --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x5573e2a1d902 <nautilus_progress_manager_has_viewers+2>: cmpq $0x0,0x20(%rdi)
 PC (0x5573e2a1d902) ok
 source "$0x0" ok
 destination "0x20(%rdi)" (0x00000020) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 nautilus_progress_manager_has_viewers ()
 ()
 g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in nautilus_progress_manager_has_viewers()
UpgradeStatus: Upgraded to artful on 2017-09-14 (4 days ago)
UserGroups: adm audio cdrom dialout dip fax lpadmin lxd netdev plex plugdev sambashare scanner sudo tape vboxusers video
usr_lib_nautilus: dropbox 2015.10.28

[Apport retracing service (apport)]

StacktraceTop:
 nautilus_progress_manager_has_viewers (self=0x0) at ../src/nautilus-progress-info-manager.c:239
 on_progress_info_finished (self=0x5573e4f3ab70, info=0x5573e766ede0) at ../src/nautilus-toolbar.c:508
 g_closure_invoke (closure=0x5573e7700750, return_value=0x0, n_param_values=1, param_values=0x7ffc1cbcd410, invocation_hint=0x7ffc1cbcd390) at ../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x5573e7c2f390, detail=detail@entry=0, instance=instance@entry=0x5573e766ede0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffc1cbcd410) at ../../../../gobject/gsignal.c:3635
 g_signal_emit_valist (instance=0x5573e766ede0, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7ffc1cbcd5d0) at ../../../../gobject/gsignal.c:3391

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[RussianNeuroMancer (russianneuromancer)]

Still issue in Ubuntu 18.10.

[Sebastien Bacher (seb128)]

Could you give specific steps you use to trigger the bug?

[RussianNeuroMancer (russianneuromancer)]

I not sure what exactly crashed it, I just got similar crash on Ubuntu 18.10, that all I know.

[Sebastien Bacher (seb128)]

Error report https://errors.ubuntu.com/problem/68df9602b1c148589a9c540e5e143ac70ebadb63

[Sebastien Bacher (seb128)]

Upstream report https://gitlab.gnome.org/GNOME/nautilus/issues/124

[Luca Ciavatta (cialu)]

I have experienced this bug in a clean 18.04.3 install.

[Sebastien Bacher (seb128)]

it's fixed in upstream git now