nautilus crashed with SIGABRT in g_assertion_message() ((source == info->idle_source))

Bug #1725745 reported by Fabio Ceccarelli
42
This bug affects 5 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Expired
Medium
Unassigned

Bug Description

crashing while drag and dropping files to copy them across two different directories opened as two nautilus tabs

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: Sat Oct 21 17:45:56 2017
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2017-10-03 (17 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/nautilus --gapplication-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
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
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: nautilus crashed with SIGABRT in g_assertion_message()
UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Fabio Ceccarelli (fabiocroma) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_assertion_message (domain=domain@entry=0x0, file=file@entry=0x555c0db5df00 "../src/nautilus-progress-info.c", line=line@entry=215, func=func@entry=0x555c0db5df20 <__func__.54357> "idle_callback", message=message@entry=0x555c0f870750 "assertion failed: (source == info->idle_source)") at ../../../../glib/gtestutils.c:2436
 g_assertion_message_expr (domain=domain@entry=0x0, file=file@entry=0x555c0db5df00 "../src/nautilus-progress-info.c", line=line@entry=215, func=func@entry=0x555c0db5df20 <__func__.54357> "idle_callback", expr=expr@entry=0x555c0db5de9e "source == info->idle_source") at ../../../../glib/gtestutils.c:2459
 idle_callback (data=0x555c0f850400, data@entry=<error reading variable: value has been optimized out>) at ../src/nautilus-progress-info.c:215
 g_timeout_dispatch (source=source@entry=0x7f7760002870, callback=<optimized out>, user_data=<optimized out>) at ../../../../glib/gmain.c:4633
 g_main_dispatch (context=0x555c0e5e95f0) at ../../../../glib/gmain.c:3148

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
Sebastien Bacher (seb128) wrote : Re: nautilus crashed with SIGABRT in g_assertion_message()

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.

information type: Private → Public
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
summary: - nautilus crashed with SIGABRT in g_assertion_message()
+ nautilus crashed with SIGABRT in g_assertion_message() ((source ==
+ info->idle_source))
tags: added: bionic
Revision history for this message
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: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]

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