A dist-upgrade is not a version upgrade.
https://help.ubuntu.com/community/AptGet/Howto#Maintenance_commands
To check your version in terminal…
Code:
inxi -S
That looks like a great way to fix it but now I really feel like an idiot.
I remember after first installing disabling grub screen either completely or dramatically reducing display time for sake of speed so now I’m not able to access it. Is there a sure fire way to access it?
Have I painted myself into a corner?
When I am able to get a cli, I will do that
Sorry, that happens when I get in a rush.
At the boot screen or at the login screen you can go to console by pressing Ctrl+Alt+F1 and log in. Console is a text only terminal.
It might be possible to access Grub by pressing the “Shift” key as soon as your PC boots?. 
Tried shift key, no go unfortunately
Kernel: 4.2.0-30-generic x86_64
Cool, Thanks, didn’t know that one. Kernel: 4.2.0-30
Ok, your running Wily.
Two things to try in console to restore GUI:
1-Press Ctrl+Alt+F7; this will try to take you to your desktop. If this fails, press Ctrl+Alt+F1 to return to console.
then try
2-While in console enter the command
startx
That may take you to the desktop (GUI).
Wimpy may return, but till then @stevecook172001 post should also work.
Ok, I restored the grub screen by following this guide: How to show grub menu in Ubuntu with only a single OS installed but using nano instead of caja because caja will not start on my system.
So I have completed the ubuntu mate update guide dpkg in recovery mode step
I can get to the desktop but the only thing that opens are menus, no windows actually open or perhaps are not visible. multiple instances of caja still opening but no windows
Is there a way to go back to default gui setting via cli? I’m no expert but that is where I believe the problem is.
Sorry stevecook172001 , didn’t repond to your suggestion and am locked out of more replys for 24 hr period, yes I believe you are right, will try to do it from cli with googles help.
Normally I would usb boot, copy data, nuke and pave when I get in a situation like this, but I need to learn to fix it as you suggest, would certainly be faster.
How did you do your initial install?, was it a disk or USB install and did you burn the disk at the slowest possible speed and/or; did you fully format the USB stick?, I ask because you seem to have multiple problems and this may be due to read/write errors when you created your bootable media?. 
Ah sorry wolfman for the answer delay. It’s on a Nuc so usb install, yeah a formatted usb via gparted. I was just getting on to say that I have created another sudo user, migrated all the data making sure not to include configs. then deleted original sudo user. From now on all my config experimentation will be in a virtual image!
1 Like
Hi,
try running the following terminal commands which may/may not solve any problems for you?:
sudo apt-get --fix-missing install
The above command downloads and installs any missing packages on your system.
sudo apt-get --fix-broken install
The above command downloads and installs any broken dependencies on your system.
Yeah I tried that before I created a new user with root privileges and deleted original root. Stetecook172001 was right, configuration issue not packages.
In hindsight I guess if I had deleted the configs that were giving me the problems then ran the commands that you suggest, I believe it would have solved the issue.
Ah well, live and learn.
1 Like
I’m not sure if this is a good place to ask for the help I need, but I’ve been Googling around a bit and this one seems to be similar, but the most up to date.
I’m using Ubuntu-Mate 16.04.2.
I just updated Mate from 1.12.1 to 1.61 using the instructions here:
Now I’m having the problem where Caja starting, infinitely! I tried going back to 1.12.1 but that didn’t solve it. I’ve also tried other things like editing the caja.desktop file with several “exec=caja -n” variations, as people have suggested, to no avail.
Has anyone figured out yet, which configuration settings that are the culprit, or was that just for wget’s grub problem?
Thanks!
I found a work around!
If anyone is still having the problem with Caja starting infinite times, look here:
http://blog.aguilarbros.com/2015/11/ubuntu-mate-multiple-caja-instances-on.html
If you don’t want to follow the link, then what I did was edit the “/usr/share/applications/caja.desktop” file where the entry is:
X-MATE-AutoRestart=true
to
X-MATE-AutoRestart=false
That solved it!
Me being such a Mate novice, I don’t know what other side effects this change will have, but it sure did the trick.
Cheers!
1 Like
OK, so this is happening again. I installed Clam antivirus and it broke Caja. Every time I boot, Caja opens 9,999 incidences and crashes the machine.
I uninstalled and purged ClamAV, which didn’t change anything. Whatever changes it made to Caja are still in effect. I downloaded and installed xfce from cli so that I could have a working system and then tried every solution I could find on the internet. Mostly changes to caja.desktop. Nothing has worked so far. Does anyone remember what this bug specifically did to caja from a few years back? I can’t use mate until I figure this out…
Mint 18.1
logged out and back in again. Problem solved.
Note: Not a Restart
PITA, but I’ve had worse
I have been having the same problem with MATE 1.12.1 (I had not switched to this desktop environment for a while) and was confronted with the problem. Even more annoying as eventually no Mate related program would start its GUI.
Changing the config of caja.desktop entry seems to have solved the problem.
PS I used the nano command (“sudo nano /usr/share/applications/caja.desktop”) as the other editors seemed not to work!
Thanks a lot.