Nemo file manager crashes 10% of the time

Thanks. Just changed it to the lowest & it didnt help, unfortunately still crashes, crashed about 5 times just now, when i try to click on folders or when i try to rename them. It wont crash initially, but if I keep renaming the same folder like 3 or 4 times in row, it crashes. Thats how i can force it to crash, and reproduce the problem. But mainly when it sometimes crashes, its simply renaming something or opening a folder merely once that causes the crashing.

Got some new error messages though.

1.)
image

___________________________________
2.)
image

________________________________________
3.)
image

I do not see anything serious or that could be clues in those warnings.

This may have to elevate to the Nemo Mint Developers.

1 Like

@DMCA_VPN , Thanks :slight_smile: Will try to.

@Aravisian , I created another login account, and created the same exact folder & file path directory, a replica, with same files too, and it didnt crash at all.

Also its not the Thumbnails option thats causing the problem, I've tried that out and it didnt change anything.

What I have noticed is that on my normal profile, nemo will crash when i'm renaming a file thats in a folder that has many other folders,videos & pics beside it.

But if I'm renaming a file that is in a small folder, with only 3 other items in it, it will never crash. (I think anyways.) Noteworthily, my RAM and CPU are still quite low & dont even peak or spike during these times when it does crash.

And there is no crashing at all on the new user account?

1 Like

Can you run nemo from terminal and see what is the error after a crash while renaming

1 Like

@Kayjzjzk , @Aravisian,

1.) To answer Aravisian's question ,the new user account, it never crashed, it has the same file directory but it doesnt have any files surrounding that directory like my main account does. I simply am not able to move all that data to the new test account. And that might be whats causing it. Its the only thing i can think of.

2.) I just tried renaming the problem folder with nemo terminal,and it never crashed. However, what i notice is when i use non terminal nemo, and keep clicking on a folder many times,opening and exiting a folder, or sometimes even just one click will crash it, no repeated clicks needed.

But as I've said before, i've found the strongest trigger to this nemo crashing, which is when i specifically try to rename a folder that has around 10 words in its folder name & a few commas. About 1 minute ago this folder caused nemo to crash, and this is what caused it:
I clicked on the particular folder thats been crashing the most, i double click to rename it, the rename/title bar is open, unsaved and with my new name in it. I click off of it, for it to save itself. It crashes the most when i change a 10 word folder title to a one word title, or vice versa.

See below, i double click to rename a folder, rename it, then click off it, for it to save and be unselected. It crashes before it even unselects & shows that it saves. It always does save, never does not save, but it crashed visually prematurely. Entire nemo shutsdown. This has happened countless times to me. It crashed even when i dont change the folder name, if I just double click to rename it & dont even change anything & then click off it to unselect & save it, it will crash. As I said in #1, i tested this in my test account & it never crashed. But may be because of lack of surrounding folders.

image

image

image

BOOM, CRASHES

On your main user account, if you backup your ~/.config

mv ~/.config ~/.config-bk

Then reboot, can you replicate the crashes?

1 Like

Thanks, I can try that. But what is in .config and what happens when I move it? will it break anything?

The above command moves (mv) the .config file which contains your configuration to a backup file called config-bk .This is to verify that the crash is not due to some user configuration.You can easily restore your system to the previous configuration by using the backup file

1 Like

@Kayjzjzk , @Aravisian ,

I did exactly as you said. The new config folder quickly filled up with stuff, i assume this is normal, it ended up quickly filling with about 10 folders of stuff compared to the normal 70 folders.
I tried to test it as quickly as possible before the config file started filling up. Here is what the new config file looks like:

It took about 15 tries of messing with the forementioned notorious problem folder to get it to crash again, but once i got it to crash it happened at an increased rate after that. It crashes often if i rename it or if i double click it to rename it, but didnt actually rename it, it would crash once i clicked off it, exactly as it was doing with my normal config folder. Also, the notorious crash causing folder isnt the only folder to cause this issue, its just one that is a good one to test.

image

Can you try renaming in Nautilus and see if that crashes too?.Thatway we can see if the bug is just in nemo or is rooted deeper in system/hardware

2 Likes

@Kayjzjzk , @Aravisian , great question Kayjzjzk. Never thought to check to see if it happens in Nautilus. I just tried it, took about 15 tries, but the crash happens in Nautilus too. I cant double click to rename in Nautilus, like I can Nemo. But I just press F2 instead. To be clear, the crashing in Nemo also happens in unprovoked low CPU/RAM situations, Nemo has crashed at random times too when i do stuff with folders, very inconvenient. And now we know Nautilus does it too.

But anyways, Yes, interestingly it happens in Nautilus & Nemo. I dont know why. I have a brand new name brand SolidState Drive too.

Give me an hour and I'll upload the log errors for nautilus, forgot about that.

1 Like

@Kayjzjzk , @Aravisian , managed to yet again replicate the crashing in nautilus, took me about 60 tries this time till it crashed. Not fun.

Here are the error logs, see three screenshots below:

image

image

image

@Kayjzjzk , @Aravisian , some more research i found:

1.)here is evidence that Nautilus & Nemo might break each other.

"Nautilus as it conflicts with Nemo and when installed some programs can prefer Nautilus instead"
https://forums.linuxmint.com/viewtopic.php?t=264132

2.) "install gtk4-debug, glib2-debug & nautilus-debug before running the backtrace" in order to diagnose cause of problem.

Perhaps, but I have both installed and never had any issues. I was also looking up information on the web and found sites claiming gthumb and other Gnome Extensions can interfere with Nautilus causing this bug, too.

1 Like

Also, someone concluded it was "a gtk issue".

@Aravisian , how do i know if i have gThumb installed?

Another possibility/problem: "The default remote repository for 13.1 seems to hang on Nautilus 42.1. Instead of 42.2"

Thats an old forum reply from 2022, but still, and also same could be said about Nemo too.

You can use apt list -i to see a list of all installed packages.

You can use a pipe: | and grep to isolate a package by name:

apt list -i | grep gthumb

1 Like