nautilus assert failure: ERROR:nautilus-window-slot.c:284:query_editor_changed_callback: assertion failed: (NAUTILUS_IS_FILE (slot->details->viewed_file))

[Andy Whitcroft]

No idea as to trigger, just appeared.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nautilus 1:3.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
Uname: Linux 3.11.0-7-generic i686
ApportVersion: 2.12.4-0ubuntu1
Architecture: i386
AssertionMessage: ERROR:nautilus-window-slot.c:284:query_editor_changed_callback: assertion failed: (NAUTILUS_IS_FILE (slot->details->viewed_file))
Date: Sat Sep 21 12:43:08 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'geometry' b"'800x540+222+31'"
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'148'
InstallationDate: Installed on 2010-05-06 (1233 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MarkForUpload: True
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=en_GB
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: nautilus
StacktraceTop:
 g_log_default_handler (log_domain=0x9c218c0 ")", log_level=-1231372270, message=0xb6976ac9 <g_slice_get_config_state+153> "\322\367\366\276\004", unused_data=0x3584b400) at /build/buildd/glib2.0-2.37.93/./glib/gmessages.c:1351
 g_strdup_printf (format=0x9c21880 "assertion failed: (NAUTILUS_IS_FILE (slot->details->viewed_file))") at /build/buildd/glib2.0-2.37.93/./glib/gstrfuncs.c:538
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: nautilus assert failure: ERROR:nautilus-window-slot.c:284:query_editor_changed_callback: assertion failed: (NAUTILUS_IS_FILE (slot->details->viewed_file))
UpgradeStatus: Upgraded to saucy on 2013-06-05 (107 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sbuild

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 ?? ()

[Sebastien Bacher (seb128)]

The bug is quite old and the code changed since, also there has been no new report of that specific problem nor activity for some years so assuming it has been resolved and closing the ticket. If you still get issues in newer versions feel free to open a new report though.