Closing the Location Options menu will hang the Nautilus window

[Cliff Carson]

Selecting the Location Option button on the Nautilus toolbar then selecting an item or just click outside the menu will cause the Nautilus window to hang and for a while make the system unresponsive.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
Uname: Linux 4.4.0-7-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Feb 24 07:11:16 2016
InstallationDate: Installed on 2015-12-19 (66 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151218)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

[Sebastien Bacher (seb128)]

Thank you for your bug report. I can't confirm that here. Does it happen on any folder/selection? Do you have high cpu or disk usage then?

[Cliff Carson (ccarson1)]

Tried two different folders selecting one file and then Invert Selection. Had the system monitor running and saw that for over a minute all four processors were running around 50%. Couldn't access anything in the system for over a minute.

[Sebastien Bacher (seb128)]

does it do it in any directory?

[Cliff Carson (ccarson1)]

OK, maybe not the Invert Selection. I got it to fail if I went to a directory selected two files and opened the Locate Options menu selected nothing and then closed the menu by clicking on the Nautilus window. The CPU activity went to about 50% for all processors but this only lasted about 10-15 sec. Was again able to access the Nautilus window.

[Cliff Carson (ccarson1)]

Yes, occurs on every directory I've tried so far.

[Cliff Carson (ccarson1)]

Another test...open Home, open the Locations option menu, close the menu (click on the Nautilus window) and the system will go unresponsive. All processors running about 50%. Had to force close Nautilus.

[Cliff Carson (ccarson1)]

Although the system is up-to-date if other people can't see this error will rebuild from daily build unless there is something I should try on this failing system.

[Cliff Carson (ccarson1)]

Rebuilt the system with the Gnome 16.04 Daily Build for 2/25. The problem continues to occur when I try to open and close the Locations Option menu in Nautilus.

[Sebastien Bacher (seb128)]

does it happen in Unity sessions as well or is that GNOME specific? could you try also in a guest session?

[Cliff Carson (ccarson1)]

Need some instruction on how to bring up a Unity session. Also can't find out how to login to a Guest ID or enable a Guest ID. Here is what I have tried.

- started a 15.10 gnome system using the same /home directory structure...no problems noticed
- created a new Standard user under the 16.04 and Nautilus failed as stated above

Willing to try anything but may need instructions on how to do it.

[Sebastien Bacher (seb128)]

could have to do with the tracker integration or something but i'm not using Ubuntu GNOME and user what might be going on there

[Cliff Carson (ccarson1)]

Just trying gather more info. Was watching the processor usage with top and saw that when I closed the Location Options menu Nautilus and gnome-shell were to top tasks running both around 50%. Only xorg was doing anything (about 9%).

[Cliff Carson (ccarson1)]

Trying to understand how the Location Options menu is closed and found in nautilus-toolbar.c a call to gtk_menu_shell_deactivate in function gear_menu_key_press. This gtk call is used to remove the menu. Don't know what the problem could be but the external symptoms of a high cpu loop between nautilus and gnome-shell is suspicious. There is no change in this function between 3.14.2 (which doesn't fail) and 3.14.3 but 3.14.3 has made changes to the construction of the Location Option button.

[Sebastien Bacher (seb128)]

hum, just to be sure, what do you call "Locations option menu"?

[Launchpad Janitor (janitor)]

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

[corrado venturini (corradoventu)]

I have the problem on Ubuntu 16.04 GNOME, not on Unity.

[Cliff Carson (ccarson1)]

The right most button on the Nautilus toolbar. Used the term Location options because when you mouse over the button that's it's title.

[corrado venturini (corradoventu)]

Nautilus and system monitor screenshot

[Sebastien Bacher (seb128)]

oh, the interface is difference under gnome-shell, looks like the issue is GNOME specific

[Cliff Carson (ccarson1)]

Have built a debug version of nautilus 3.14.3 but not being gdb fluent don't know how to stop the loop condition to see where it is occurring. Did place a breakpoint in the nautilus.toolbar.c where the button click gets control and saw the gdb indicate at that location but the system was locked up and had to power-off/on to free it. Based on the way this is failing I don't see where in nautilus code to place breakpoints. It looks like the failure is occurring outside nautilus. Maybe freeing up the menu resources?

[heiko (heikosch)]

Just installed nautilus 3.18.5-0ubuntu1 from the Gnome3 Team repository (ppa:gnome3-team/gnome3) and the issue is gone - at least for me.

[Cliff Carson (ccarson1)]

Install nautilus 3.18.5 and the high cpu problem is gone but the "location option" menu appears to be incomplete. Missing some of the select options (invert selection) and the call to open a shell.

[heiko (heikosch)]

To open in terminal one should right click on the white space or on the desired folder to bring up a context menu where you'll find that option. Just my 2ct ;)

[Cliff Carson (ccarson1)]

Thanks, didn't look around much just determined that closing the menu didn't cause a loop between nautilus and gnome-shell. Screw up the removal of 3.18.5 or the re-installation of 3.14.4 but had to rebuild the system to recover. Just for my own interest still trying to understand where this loop is occurring so back to gdb on 3.14.4.

[Cliff Carson (ccarson1)]

Need help debugging this problem. Have a debug version of nautilus and get it up and reproduce the loop but don't have enough gdb experience to understand where this loop is taking place. Did find using the NAUTILUS_DEBUG environmental variable you can stop and examine the threads (4 in most cases) but this doesn't help me. Will be happy to try whatever anyone suggest but for right now I'm out of ideas.

[Cliff Carson (ccarson1)]

Installed Gnome 16.10 and the problem still exists.

[hsquared (hsquared)]

Can confirm aswell.

[Cliff Carson (ccarson1)]

The update to Nautilus 1:3.20.1-0ubuntu2 has remove this problem although there is no menu pull-down that contains "Invert Selection". The CTL-Shift-I does provide this function.

[Sebastien Bacher (seb128)]

thanks, closing the bug then