Frequent crashes

[BillDietrich]

I'm a n00b; sorry if I'm doing this wrong.

 * Nemo version   4317 ?
 * Is issue with desktop or windowed nemo?  Windowed, I think
 * Distribution - Linux Mint 19 Tara
 * Graphics hardware *and* driver used:  Intel Core Processor Integrated Graphics Controller
 * 32 or 64 bit:  64

Issue

After doing a lot of downloading (via Firefox or Tor) and/or a lot of moving files around, maybe from internal disk to USB disk or USB flash drive, nemo crashes (all nemo windows disappear). I can start it again, no problem. Happens about once a day, on average.

Steps to reproduce

Expected behaviour

Other information
inxi.txt
trace.txt
xsession-errors.txt
xsession-errors-old.txt

[jaszhix]

If you're using extensions, try disabling them. The included trace won't be helpful because no symbols are installed.

sudo apt install nemo-dbg

[BillDietrich]

By "extensions", you mean add-ons in Firefox ? But I've had nemo crash when I was just copying files in nemo.

I did following in response to your comment:

$ sudo apt install nemo-dbg
[sudo] password for user1:
Reading package lists... Done
Building dependency tree
Reading state information... Done
nemo-dbg is already the newest version (3.8.5+tara).
The following packages were automatically installed and are no longer required:
kded5 kdenlive-data libebur128-1 libjsoncpp1 libkf5bookmarks-data libkf5bookmarks5 libkf5kiofilewidgets5 libkf5newstuff-data libkf5newstuff5
libkf5newstuffcore5 libmagick++-6.q16-7 libmlt++3 libmlt-data libmlt6 libmovit8 libopenshot-audio6 libopenshot14 libqt5designer5 libqt5help5 libqt5test5
librtaudio6 libsox3 linux-headers-4.15.0-29 linux-headers-4.15.0-29-generic linux-headers-4.15.0-30 linux-headers-4.15.0-30-generic
linux-image-4.15.0-29-generic linux-image-4.15.0-30-generic linux-modules-4.15.0-29-generic linux-modules-4.15.0-30-generic melt python3-openshot
python3-pyqt5 python3-pyqt5.qtsvg python3-pyqt5.qtwebkit python3-sip python3-zmq
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

This seems to say nemo-dbg already was installed ? If so, and I just need to run nemo-dbg instead of nemo, how do I get nemo-dbg to run by default ? Thanks.

[leigh123linux]

Please post the output for

/usr/lib/*/nemo/nemo-extensions-list

And they can be disabled using nemo menu: edit / plugins /

[jaszhix]

Looking at your xsession-errors, you're using the Dropbox extension. Its crashed Nemo for me before - in Nemo go to Edit -> Plugins -> Uncheck Dropbox under Extensions.

[BillDietrich]

$ /usr/lib/*/nemo/nemo-extensions-list
Initializing nemo-dropbox 3.8.0
NEMO_EXTENSION:::EmblemPropertyPage+NemoPython:::Nemo Emblems:::Change a folder or file emblem
NEMO_EXTENSION:::ChangeColorFolder+NemoPython
NEMO_EXTENSION:::NemoFileRoller:::Nemo Fileroller:::Allows managing of archives from the context menu
NEMO_EXTENSION:::NemoShare:::Nemo Share:::Allows you to quickly share a folder from the context menu
NEMO_EXTENSION:::NemoDropbox:::Nemo DropBox:::Allows managing of Dropbox web service from the context menu

[BillDietrich]

Okay, will disable most extensions (including Dropbox) and see if the crashes stop. How can I set nemo-dbg as default ?

[jaszhix]

Sorry, misread the trace file - nemo symbols are showing up.

[BillDietrich]

Nemo just crashed again. I had removed a USB external disk (properly, got notification it was safe to unplug), then I was trying to open files in Atom, went to Nemo to look at the folder of files to see if that was a better way to open them, and boom! nemo disappeared. I did a lot of playing and copying/deleting video files earlier today; I think that's relevant.

I see that /usr/lib/*/nemo/nemo-extensions-list says I have 5 extensions installed or enabled, but in Edit/Plugins yesterday I disabled all but the fileroller extension. It still shows that way today before and after the nemo crash; 5 extensions installed but only one (fileroller) enabled.

There are various alarming messages in the following files; maybe I have more problems than just a nemo problem ?

dmesg.txt
inxi.txt
nemoexts.txt
trace.txt
xsession-errors.txt

[BillDietrich]

I removed everything Dropbox-related, and the system was good for a couple of days. Then nemo crashed while I was away from the system and the lock screen was up.

crash.tar.gz
nemo-extensions.txt
xsession-errors.txt

[BillDietrich]

Okay, I found what's causing it. I'm using https://github.com/KenMacD/wdpassport-utils to mount and decrypt a WD My Passport Ultra external hard drive. If I mount and unmount that drive a couple of times using some of that software, nemo crashes. I suspect the software is leaving some field empty in a mount table or device table or something, and nemo doesn't expect that.

Maybe the problem is occurring at an even more basic level, and doesn't require use of that software. If I plug in the drive, immediately a read-only "WD Unlocker" device/drive is mounted (this is normal, it is used under Windows to provide an app to decrypt and mount the real drive). But if I then unmount and try to "eject" that drive, I get an error from the eject command (see attached screenshot). The decryption software mentioned above has not been used in this scenario.

[BillDietrich]

Plugged in the WD drive and did this:

$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 1.4G 0 1.4G 0% /dev
tmpfs 287M 1.4M 286M 1% /run
/dev/sda5 33G 16G 16G 51% /
tmpfs 1.4G 26M 1.4G 2% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 1.4G 0 1.4G 0% /sys/fs/cgroup
/dev/sda1 945M 361M 520M 41% /boot
/dev/sda6 259G 117G 130G 48% /home
tmpfs 287M 40K 287M 1% /run/user/1000
/home/user1/.Private 259G 117G 130G 48% /home/user1
/dev/sdb1 7.5G 175M 7.3G 3% /media/user1/C930-7D6F
/dev/sr1 13M 13M 0 100% /media/user1/WD Unlocker13
$ sudo tune2fs -l /dev/sr1
[sudo] password for user1:
tune2fs 1.44.1 (24-Mar-2018)
tune2fs: Bad magic number in super-block while trying to open /dev/sr1
/dev/sr1 contains a udf file system labelled 'WD Unlocker'
$

[mtwebster]

Hi, assuming you're still on Mint 19 64 bit, can you try the packages here?

https://www.dropbox.com/sh/kfc8mvw140x207x/AACAa-s9VkPwdszIiy3g_aRba?dl=0

Download them to a folder, open a terminal, and run:

sudo dpkg -i *nemo*.deb

Then log out and back in, and let me know if the behavior you're seeing changes.

The commit I reference above should fix the crashes, though I'm not sure it will do anything beyond that for any mount/unmount issues you might be having.

If you want to revert back to the published version, just refresh mintupdate, and it will want to reinstall its version (the one I have here is considered a 'lower' version and the package manager will want to upgrade it.)

Thanks

[BillDietrich]

Installing that, I got:

Setting up libnemo-extension1:amd64 (3.8.5) ...
dpkg: dependency problems prevent configuration of libnemo-extension-dev:
 libnemo-extension-dev depends on libglib2.0-dev (>= 2.45.7); however:
  Package libglib2.0-dev is not installed.
  libnemo-extension-dev depends on libgtk-3-dev (>= 3.9.10); however:
  Package libgtk-3-dev is not installed.

dpkg: error processing package libnemo-extension-dev (--install):
 dependency problems - leaving unconfigured

Then I tried:

$ sudo apt-get install libglib2.0-dev
Reading package lists... Done
Building dependency tree       
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 libglib2.0-dev : Depends: libglib2.0-dev-bin (= 2.56.1-2ubuntu1)
                  Depends: libpcre3-dev (>= 1:8.31) but it is not going to be installed
                  Depends: zlib1g-dev but it is not going to be installed
 libnemo-extension-dev : Depends: libgtk-3-dev (>= 3.9.10) but it is not going to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).

So now I don't know where I am. Will reboot and see if nemo works.

[BillDietrich]

That seems to have fixed it ! I can't get nemo to crash any more. Tried various combinations of plugging and unplugging drive, dismounting and ejecting it, using it for a while, etc. Thanks !

I still see "unable to eject; invalid argument" (see screenshot of the dialog in an earlier comment). Is that a nemo problem ?

[mtwebster]

Ah sorry I shouldn't have had you install the -dev package, it's not really necessary. Try sudo dpkg -r libnemo-extension-dev or sudo apt-get install -f to fix that situation.

The invalid argument I don't think could be a nemo problem unless it's somehow causing that eject command to be called more than once (This is what I suspect may be happening - the script runs a first time, succeeds, then is run again for some unknown reason, at which point /dev/sr1 no longer exists, causing the error dialog)

Perhaps look in the system udev folders, maybe you have more than one handler acting on this disk when the eject command is called. I'm not an expert on this, but look in /lib/udev/rules.d and /etc/udev/rules.d - you're using this 3rd-party utility, maybe there's a default rule for these devices that needs to be disabled?

[RenatoSalles007]

Bonjour,
I have an Linux Mint 19.3 Cinnamon and nemo crashs every single time i open a folder which has 2 .mp4 files. I had to isolate this folder from a bunch of jpg's and other image files from preventing that crashes. Does anybody can point me to a sol/workaround?
Cheers,
RSalles

[xenopeek]

@RenatoSalles007 as the original issue here was fixed as reported above, suggest you create a new issue for it. Please try reproducing it on Linux Mint 20 Cinnamon.