nautilus hangs on file delete

[peterzay]

Nautilus hangs when deleting a file. The file does not get deleted. This applies to the DELETE key, the SHIFT+DELETE keys, and the RIGHT-CLICK attempt at deleting.

This is reproducible in this boot session.

This has never happened since the install of the OS.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: nautilus 1:3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 26 18:12:36 2019
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:

InstallationDate: Installed on 2019-10-20 (6 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191014)
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

[Sebastien Bacher (seb128)]

Thank you for your bug report. Do you mean it hangs on a specific file an only this one?
Could you
- give details on the file/location? is it a local directory or a remote mount?
- add your 'journalctl -b 0' log after getting the issue?
- try to use gdb to get a backtrace of nautilus while it's hanging? (https://wiki.ubuntu.com/Backtrace#Already_running_programs)

[peterzay (peterzay)]

>Do you mean it hangs on a specific file
No, any file.

>give details on the file/location
~/Downloads

I had to end the nautilus process in System Monitor.

The power down button in the upper right corner of the desktop did not work. No response at all.

I had to issue the reboot command from terminal.

Upon reboot, everything was back to normal.

By the way, the power down button does not work at all from the user list you get just after each boot. This is reproducible across several boot sessions.

[Sebastien Bacher (seb128)]

So the hang issue went away? Can you still add the journalctl log from the session where you had the issue?.

the power button not working on the login screen is bug #1847896

[peterzay (peterzay)]

>So the hang issue went away
Yes, the reboot wiped everything clean.

>Can you still add the journalctl log from the session where you had the issue
There is a lot of private information in the log, computer name, file names, paths, that should not be publicly posted.

There are also a lot of errors of various types.

What do you suggest?

[Sebastien Bacher (seb128)]

is there any nautilus or gvfs errors/warnings in the log? could you post those (replacing private name/path if needed)?

[peterzay (peterzay)]

You will find attached the journalctl log for the corrupted session.

It has been anonymized.

[Nico Rikken (nico-rikken)]

I too have this issue. I just upgraded from 18.04 LTS to 19.10 and Nautilus starts fine, finishes the check, but I cannot initiate any file commands like copy, move or delete. Nautilus doesn't respond and GNOME serves the pop-up to kill Nautilus. Pressing the 'waiting' option repeatedly doesn't solve it.

Running it from the commandline, I see some widget errors when trying to execute a command:

$ nautilus
G
(org.gnome.Nautilus:23240): Gtk-CRITICAL **: 21:55:52.377: gtk_widget_get_mapped: assertion 'GTK_IS_WIDGET (widget)' failed

(org.gnome.Nautilus:23240): Gdk-CRITICAL **: 21:55:52.377: gdk_window_is_visible: assertion 'GDK_IS_WINDOW (window)' failed

(org.gnome.Nautilus:23240): Gdk-CRITICAL **: 21:55:52.377: gdk_window_show_internal: assertion 'GDK_IS_WINDOW (window)' failed

(org.gnome.Nautilus:23240): Gtk-CRITICAL **: 21:55:52.377: gtk_widget_set_opacity: assertion 'GTK_IS_WIDGET (widget)' failed

(org.gnome.Nautilus:23240): Gtk-CRITICAL **: 21:55:52.377: gtk_widget_queue_draw: assertion 'GTK_IS_WIDGET (widget)' failed

(org.gnome.Nautilus:23240): Gtk-CRITICAL **: 21:55:54.380: gtk_widget_get_mapped: assertion 'GTK_IS_WIDGET (widget)' failed

(org.gnome.Nautilus:23240): Gdk-CRITICAL **: 21:55:54.380: gdk_window_is_visible: assertion 'GDK_IS_WINDOW (window)' failed

(org.gnome.Nautilus:23240): Gtk-CRITICAL **: 21:55:54.380: gtk_widget_set_opacity: assertion 'GTK_IS_WIDGET (widget)' failed

(org.gnome.Nautilus:23240): Gtk-CRITICAL **: 21:55:54.380: gtk_widget_queue_draw: assertion 'GTK_IS_WIDGET (widget)' failed

It seems this bug has been reported upstream too, but is ignored as the version is too old https://gitlab.gnome.org/GNOME/nautilus/issues/1218

I cannot find an easy answer in the logs that points to a specific problem.

I can successfully do the file operations from the command line using mv, cp and rm, so it is no permission issue.

I'm now in the process of installing Nautilus from Flathub gnome-nightly, hopefully that will give me back a working system. Because even though I did a nice upgrade using `sudo do-release-upgrade` it feels like I have a broken system now.

Is there a way I can get more debugging from Nautilus?

[Nico Rikken (nico-rikken)]

Alright, to confirm, installing the org.gnome.NautilusDevel and running it has given me a working system again. In case somebody is looking for a way to get a working system until 20.04 lands.

[chachi5983 (chachi5983)]

I had the same issue today, and I remember the last thing I done yesterday before failing was installing the MegaSync extension. I have just removed that package and restarted and Nautilus is working again.
I hope this would be useful.

[Launchpad Janitor (janitor)]

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