nautilus crashed with SIGSEGV in nautilus_progress_manager_has_viewers()

Bug #1718135 reported by GuiroZ on 2017-09-19
46
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Nautilus
New
Unknown
nautilus (Ubuntu)
Medium
Unassigned

Bug Description

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

GuiroZ (riccardo-bozzo) wrote :

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

Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Launchpad Janitor (janitor) wrote :

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

Changed in nautilus (Ubuntu):
status: New → Confirmed

Still issue in Ubuntu 18.10.

Sebastien Bacher (seb128) wrote :

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

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

Sebastien Bacher (seb128) wrote :
Changed in nautilus (Ubuntu):
status: Confirmed → Triaged
Changed in nautilus:
status: Unknown → New
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.