nautilus crashed with SIGABRT

[El jinete sin cabeza]

https://gitlab.gnome.org/GNOME/nautilus/-/issues/1426

---

I was working with: NAS(samba) + nautilus search bar in folder of NAS.

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.0-1ubuntu1
Uname: Linux 5.6.0-050600rc7-generic x86_64
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 27 14:35:37 2020
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2018-12-02 (480 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcCmdline: /usr/bin/nautilus --gapplication-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=es_CL:es
 LANG=es_CL.UTF-8
Signal: 6
SourcePackage: nautilus
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ()
 nautilus_window_slot_open_location_full ()
 () at /usr/lib/x86_64-linux-gnu/libffi.so.7
Title: nautilus crashed with SIGABRT
UpgradeStatus: Upgraded to focal on 2018-12-02 (480 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:

usr_lib_nautilus:

[Apport retracing service (apport)]

StacktraceTop:
 g_assertion_message.cold () from /tmp/apport_sandbox_p3p3qyhz/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /tmp/apport_sandbox_p3p3qyhz/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 begin_location_change (self=0x557c759c0c20, location=0x7f9490028750, previous_location=<optimized out>, new_selection=<optimized out>, type=NAUTILUS_LOCATION_CHANGE_STANDARD, distance=0, scroll_pos=0x0) at ../src/nautilus-window-slot.c:1450
 nautilus_window_slot_open_location_full (self=0x557c759c0c20, location=0x7f9490028750, flags=<optimized out>, new_selection=0x0) at ../src/nautilus-window-slot.c:1291
 ffi_call_unix64 () at ../src/x86/unix64.S:101

[El jinete sin cabeza (ejsc)]

https://gitlab.gnome.org/GNOME/nautilus/-/issues/1426

[Sebastien Bacher (seb128)]

Upstream closed the bug with that statement

> I can't reproduce this with 43.1. If someone can still reproduce, feel free to reopen.

Doing the same for Ubuntu since we have that version now and no recent report nor activity