nautilus crashed with SIGABRT in g_assertion_message(), while/after moving large file (file->details->directory == directory)

Bug #1726643 reported by Derek Hall
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Moved 1.2GB .mp4 from Desktop to Home. Nautilus crashed (apparently after the move was complete)

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
Uname: Linux 4.13.0-16-lowlatency x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Oct 24 01:00:40 2017
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2017-08-02 (82 days ago)
InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215)
ProcCmdline: /usr/bin/nautilus file:///home/username
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: nautilus
StacktraceTop:
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 nautilus_directory_async_state_changed ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGABRT in g_assertion_message()
UpgradeStatus: Upgraded to artful on 2017-10-21 (2 days ago)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Derek Hall (derek-hall-hp) wrote :
tags: removed: need-amd64-retrace
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_assertion_message (domain=domain@entry=0x0, file=file@entry=0x55f3cda3df20 "../src/nautilus-directory-async.c", line=line@entry=4340, func=func@entry=0x55f3cda3e6a0 <__func__.62543> "filesystem_info_stop", message=message@entry=0x55f3cf86daf0 "assertion failed: (file->details->directory == directory)") at ../../../../glib/gtestutils.c:2436
 g_assertion_message_expr (domain=domain@entry=0x0, file=file@entry=0x55f3cda3df20 "../src/nautilus-directory-async.c", line=line@entry=4340, func=func@entry=0x55f3cda3e6a0 <__func__.62543> "filesystem_info_stop", expr=expr@entry=0x55f3cda3e050 "file->details->directory == directory") at ../../../../glib/gtestutils.c:2459
 filesystem_info_stop (directory=0x55f3cf4a5d70) at ../src/nautilus-directory-async.c:4340
 start_or_stop_io (directory=0x55f3cf4a5d70) at ../src/nautilus-directory-async.c:4670
 nautilus_directory_async_state_changed (directory=directory@entry=0x55f3cf4a5d70) at ../src/nautilus-directory-async.c:4751

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
summary: nautilus crashed with SIGABRT in g_assertion_message(), while/after
- moving large file
+ moving large file (file->details->directory == directory)
information type: Private → Public
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
Derek Hall (derek-hall-hp) wrote : Re: [Bug 1726643] Re: nautilus crashed with SIGABRT in g_assertion_message(), while/after moving large file (file->details->directory == directory)

Upstream bug link:-

https://gitlab.gnome.org/GNOME/nautilus/issues/335

On 26/03/18 16:15, Sebastien Bacher 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
Sebastien Bacher (seb128) wrote :

thanks!

Changed in nautilus (Ubuntu):
status: New → Triaged
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.