Arch Linux

Dowefu

Member

Registered: 2014-03-25

Posts: 68

Nautilus.desktop

Nautilus doesn't start from the desktop-file after the system update.

When I click to the desktop-file to start Nautilus, the program is loading some time and then its icon hangs in the GNOME dock but the window doesn't show up. If then I right-mouse-click to this icon and choose “New window”, the Nautilus window appears and the program works without any issues. However after the system restart the problem appears again.

How to restore the normal start of the program from the desktop-file?

Here's the content of the desktop-file:

[Desktop Entry]
Name=Files
Comment=Access and organize files
Keywords=folder;manager;explore;disk;filesystem;
Exec=nautilus --new-window %U
Icon=system-file-manager
Terminal=false
Type=Application
DBusActivatable=true
StartupNotify=true
Categories=GNOME;GTK;Utility;Core;FileManager;
MimeType=inode/directory;application/x-gnome-saved-search;
X-GNOME-Bugzilla-Bugzilla=GNOME
X-GNOME-Bugzilla-Product=nautilus
X-GNOME-Bugzilla-Component=general
X-GNOME-Bugzilla-Version=3.14.2
X-GNOME-UsesNotifications=true

GNOME 3.14.2

Last edited by Dowefu (2015-03-31 10:07:54)

ooo

Member

Registered: 2013-04-10

Posts: 1,638

Re: Nautilus.desktop

Have you enabled desktop icons with gnome/nautilus by any chance? There was a bug that causes similar behavior that you reported if they are enabled.

Dowefu

Member

Registered: 2014-03-25

Posts: 68

Re: Nautilus.desktop

As it turned out, it needed to remove the `~/.config` directory. Although I have to reconfigure some of the applications, the bug disappeared.

ayekat

Member

Registered: 2011-01-17

Posts: 1,634

Re: Nautilus.desktop

As it turned out, it needed to remove the `~/.config` directory. Although I have to reconfigure some of the applications, the bug disappeared.

For future reference (a.k.a. people seeking for help in this thread), it's hardly ever a good idea to nuke the entire ~/.config folder. Usually an application specific configuration is in a subfolder (probably ~/.config/Nautilus - I don't use it so I don't know exactly), so it should be enough to delete that one.

Of course, if some other program interferes with Nautilus in a way that it makes it bug, it's a little harder to pinpoint the reason for a misbehaviour, and if you prefer the point-and-click approach, I assume you don't manually edit configuration files in ~/.config, so it won't hurt you much.

EDIT
Now that I think about it, I guess that the people who manually edit ~/.config files will actually go through the aforementioned thought process before laying ~/.config into ashes, and so my post may make less sense than I thought it would when I started typing it.

Last edited by ayekat (2015-03-31 14:27:45)

---

pkgs │ hacks │ cfg │ blag