Nemo refuses to access folders

LenSessions · 11-16-2020, 08:30 PM

There are folders that appear in my tree view - they even expand to show their sub-folders - but when I click on them Nemo refuses to show any of the files in those folders. The address bar doesn’t even indicate that I have clicked on it - it still shows the name of the previous folder I’d been in.
These are folders that Nemo HAS accessed in the past but won’t any more, and I have no idea what changed.
Other file managers can still access those folders but Nemo refuses to.
I’ve been unable to find anyone else who’s had this problem, possibly because my search terms are too generic. Any thoughts?

frankbell · 11-16-2020, 09:26 PM

From Nemo's right-click menu (I don't use Nemo but I assume it has one), what does Nemo tell you about the permissions of those directories? Alternatively, from the command line, what does

Code:

ls -l

tell you about their permissions?

See man ls for more.

LenSessions · 11-17-2020, 10:20 PM

For both accessible and inaccessible folders Nemo shows me as owner with permission to create and delete files.
And from the command line, accessible and inaccessible folders both seem to be drwxrwxrwx.
Other file managers can still access the folders that Nemo can’t - which is both weird and possibly a clue to what’s going on here.

LenSessions · 11-18-2020, 01:01 PM

“Have you tried turning it off and on again?”
If anyone else has this issue, you can just rename the unviewable directory then change it back again.
But it sure would be nice to understand what’s actually happening and why.

frankbell · 11-18-2020, 07:19 PM

Try starting Nemo from the command line and accessing an available folder, then one of the unavailable ones.

See whether Nemo throws anything helpful to the terminal; if it does, post it here, being sure to surround it with "code" tags, which appear on the menu when you click the "Go Advanced" button beneath the compose/edit post window.

LenSessions · 11-24-2020, 08:23 PM

First of all, let me apologize for being a bit of a Linux noob. I spent most of my life as a Windows guy and I suspect my shortcomings with Linux are about to become apparent.
I’d never launched Nemo from the command line before. Doing so seemed to make no difference to the ability to access or not access folders, and nothing of interest appeared in the terminal.
I then tried to get creative and launch Nemo in a specific folder (hoping eventually to launch in an inaccessible folder).
It took me a while to work out how to do that even with an accessible folder but I did get some activity in the terminal (before Nemo promptly crashed). I don’t know if any of this is relevant to my original problem:

Code:

(nemo:32057): Gtk-WARNING **: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

** (nemo:32057): CRITICAL **: fm_tree_model_get_value: assertion 'iter_is_valid (FM_TREE_MODEL (model), iter)' failed

(nemo:32057): GLib-GObject-WARNING **: /build/glib2.0-Rpbmm0/glib2.0-2.48.2/./gobject/gtype.c:4273: type id '0' is invalid

(nemo:32057): GLib-GObject-WARNING **: can't peek value table for type '<invalid>' which is not currently referenced
Segmentation fault

frankbell · 11-24-2020, 09:36 PM

Quote:

First of all, let me apologize for being a bit of a Linux noob.

LenSessions, please don't apologize for being new to Linux. We were all newbies once.

That this occurs in Nemo and not in other file managers leads me to think that this might be a bug in Nemo.

You might consider filing a bug report or at least reviewing the Nemo bug reports that have already been filed. https://github.com/linuxmint/nemo/issues

Full disclosure: My preferred GUI file manager is Dolphin. I'm not a big fan of KDE/Plasma as a desktop environment (I usually use the Fluxbox window manager), but I do rather like KDE/Plasma applications and tend to default o them.

ondoho · 11-25-2020, 12:13 AM

Quote:

Originally Posted by LenSessions

I’d never launched Nemo from the command line before.

Since nemo is probably already running (as a daemon and/or managing the desktop) this probably won't help much.
Although the Segmentation fault in your output does seem to tell us something.

Sorry, but we really need an

Code:

ls -al

of the folder(s) in question. See post #2.

LenSessions · 12-03-2020, 08:39 AM

Quote:

Originally Posted by frankbell

That this occurs in Nemo and not in other file managers leads me to think that this might be a bug in Nemo.

That seemed logical to me, but I also wasn’t sure if I‘d done something to cause the issue. I’d been using Nemo happily for months before this started happening. Having looked at the bugs on github, though, something similar does seem to have been reported although that was over 2 years ago!
If it’s a known bug, I’ll just use workarounds for the next few months til I upgrade this PC. When I installed Linux on this 10yr old 32-bit machine it was meant to be an experiment but instead I just never went back to Windows.
In my Windows days I was the tech guy in the family, but I’ve only learned enough about Linux to “get by”, so it’s a bit of a comedown.

For a little amusement, though, when I run "ls -al", I get this. Guess which folder is the inaccessible one.

drwxrwxrwx 1 lensessions lensessions 4096 Nov 25 19:35 .
drwxrwxrwx 1 lensessions lensessions 24576 Nov 18 18:20 ..
drwxrwxrwx 1 lensessions lensessions 4096 Oct 7 13:56 archive
drwxrwxrwx 1 lensessions lensessions 28672 Nov 24 15:58 K
drwxrwxrwx 1 lensessions lensessions 4096 Nov 23 17:53 L
drwxrwxrwx 1 lensessions lensessions 94208 Nov 22 04:12 L&K