Sorry, I still cant find it with the advanced menu. I can find it in the classic menu.
It only appears in the classic menu as far as I know.
I have a question as I donāt have ubuntu mate installed any longer. If I were to do a fresh install and choose to download updates during installation will that give me Mate 1.14?
My apologies I believe the question I asked below is answered here.
It will not, as Mate 1.14 is only available via a PPA right now.
See this thread for details on how to upgrade to 1.14.
Hereās one way of getting the About Dialogā¦ Hit Alt+F2 then type the following:
mate-about
1 Like
Can you guys name some of the features in the release notes that make this update worthwhile?
It seems that most of what makes 1.14 a valuable Mate version is the definite move to GTK3, but since our PPA includes a version built against GTK2+, until we get Ubuntu-Mate 16.10 and GTK3 by default, we are only left with those features in the release notes that improve the current MATE applications. But I canāt find anything worthwhile in there.
At first glance Iām not seeing an advantage in adding this PPA to the 16.04 line. Would you agree?
4 Likes
I think the GTK2 build is basically a bugfix release. I didnāt come across any new features either.
1 Like
I with change, Ubuntu Mate starts and better off, now turn off in 5 seconds
2 Likes
Is it possible to add it manually to the advanced menu like in the classic menu?
I think there is an options button on the advanced menu, āPreferencesā?. 
1 Like
Thank you . Installing now.
You can get it by pressing ALT+F2 and entering mate-about .
1 Like
The PPA is fixed 
1 Like
Just installed the PPA for MATE 1.14 and so far Iām impressed. The only bug Iāve found is that it seems MATE is picky on where you can use apt update && apt upgrade && apt dist-upgrade.
If I enter the terminal and paste sudo apt update && sudo apt upgrade && sudo apt dist-upgrade, I get the following:
santafe@santafe-Dell-DXP051:~$ sudo apt update && apt upgrade && apt dist-upgrade
[sudo] password for santafe:
Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Ign:2 http://dl.google.com/linux/earth/deb stable InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:4 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease
Hit:5 http://dl.google.com/linux/earth/deb stable Release
Hit:6 http://archive.canonical.com/ubuntu xenial InRelease
Get:7 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]
Hit:8 http://ppa.launchpad.net/appgrid/stable/ubuntu xenial InRelease
Hit:9 http://ppa.launchpad.net/embrosyn/cinnamon/ubuntu xenial InRelease
Ign:10 http://download.videolan.org/pub/debian/stable InRelease
Hit:11 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial InRelease
Hit:12 http://download.videolan.org/pub/debian/stable Release
Hit:13 http://ppa.launchpad.net/mc3man/mpv-tests/ubuntu xenial InRelease
Hit:14 http://ppa.launchpad.net/no1wantdthisname/ppa/ubuntu xenial InRelease
Hit:15 http://ppa.launchpad.net/rvm/smplayer/ubuntu xenial InRelease
Hit:17 http://ppa.launchpad.net/trebelnik-stefina/solaar/ubuntu xenial InRelease
Hit:18 http://ppa.launchpad.net/ubuntu-mate-dev/welcome/ubuntu xenial InRelease
Hit:19 http://ppa.launchpad.net/ubuntu-mate-dev/xenial-mate/ubuntu xenial InRelease
Hit:20 http://ppa.launchpad.net/webupd8team/java/ubuntu xenial InRelease
Fetched 94.5 kB in 2s (37.1 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?
santafe@santafe-Dell-DXP051:~$ However, I have an alias in my .bash_aliases file called DUpdate that looks like this: alias DUpdate=āsudo apt update && sudo apt upgrade && sudo apt dist-upgradeā and when I run it this happens:
santafe@santafe-Dell-DXP051:~$ DUpdate
Ign:1 http://dl.google.com/linux/earth/deb stable InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:4 http://dl.google.com/linux/earth/deb stable Release
Hit:5 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease
Hit:6 http://ppa.launchpad.net/appgrid/stable/ubuntu xenial InRelease
Hit:7 http://archive.canonical.com/ubuntu xenial InRelease
Get:8 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]
Ign:9 http://download.videolan.org/pub/debian/stable InRelease
Hit:10 http://ppa.launchpad.net/embrosyn/cinnamon/ubuntu xenial InRelease
Hit:11 http://download.videolan.org/pub/debian/stable Release
Hit:12 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial InRelease
Hit:13 http://ppa.launchpad.net/mc3man/mpv-tests/ubuntu xenial InRelease
Hit:15 http://ppa.launchpad.net/no1wantdthisname/ppa/ubuntu xenial InRelease
Hit:16 http://ppa.launchpad.net/rvm/smplayer/ubuntu xenial InRelease
Hit:17 http://ppa.launchpad.net/trebelnik-stefina/solaar/ubuntu xenial InRelease
Hit:18 http://ppa.launchpad.net/ubuntu-mate-dev/welcome/ubuntu xenial InRelease
Hit:19 http://ppa.launchpad.net/ubuntu-mate-dev/xenial-mate/ubuntu xenial InRelease
Hit:20 http://ppa.launchpad.net/webupd8team/java/ubuntu xenial InRelease
Fetched 94.5 kB in 2s (36.4 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
santafe@santafe-Dell-DXP051:~$ Is this a bug, or what? Seems to me if it gives me errors when I run it in the terminal, but doesnāt when itās in an alias command, thatās a bit confusing. 
sudo apt update && sudo apt upgrade, and sudo apt update && sudo apt dist-upgrade works normally though.
EDIT: Ignore this post, it was a brain fart. As it was pointed out to me, I forgot two pesky SUDOs. 
1 Like
Hey
According to your first log you forgot two "sudo"s in your first command. :)
1 Like