nautilus crashed with SIGSEGV in nautilus_window_slot_get_allow_stop()

Bug #1724975 reported by italo maia
56
This bug affects 7 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Fix Released
High
Marco Trevisan (Treviño)

Bug Description

I'm really unsure what caused it. Log says the problem is related to a report.py script block of code.

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
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 17:19:51 2017
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2017-10-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/nautilus --gapplication-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, user)
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.UTF-8
SegvAnalysis:
 Segfault happened at: 0x55ae0dd0b387 <nautilus_window_slot_get_allow_stop+7>: mov 0x98(%rdi,%rax,1),%eax
 PC (0x55ae0dd0b387) ok
 source "0x98(%rdi,%rax,1)" (0xfffffffffffffe78) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 nautilus_window_slot_get_allow_stop ()
 nautilus_window_sync_allow_stop ()
 nautilus_files_view_update_toolbar_menus ()
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in nautilus_window_slot_get_allow_stop()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
italo maia (imaia) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 nautilus_window_slot_get_allow_stop (self=self@entry=0x0) at ../src/nautilus-window-slot.c:3057
 nautilus_window_sync_allow_stop (window=0x55ae0e808490, slot=0x0) at ../src/nautilus-window.c:887
 nautilus_window_reset_menus (window=<optimized out>) at ../src/nautilus-window.c:869
 nautilus_files_view_update_toolbar_menus (view=0x55ae0ef22a90) at ../src/nautilus-files-view.c:8130
 on_end_file_changes (view=0x55ae0ef22a90) at ../src/nautilus-files-view.c:4038

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in nautilus (Ubuntu):
status: New → Confirmed
Changed in nautilus (Ubuntu):
importance: Medium → High
information type: Private → Public
Revision history for this message
Sebastien Bacher (seb128) wrote :

similar reports against the fedora version https://bugzilla.redhat.com/show_bug.cgi?id=1464086

Revision history for this message
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 https://wiki.ubuntu.com/Bugs/Upstream/GNOME. 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.

Revision history for this message
Marco Trevisan (Treviño) (3v1n0) wrote :
Changed in nautilus (Ubuntu):
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
status: Confirmed → In Progress
Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue has been fixed with 3.26.3 in bionic

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

Other bug subscribers

Remote bug watches

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