I remember hearing about it back then but never really bothered with it as there was xfce in the official Debian repos and mate wasn't. Now it is being added to Debian unstable and testing, that means it will be available in the next stable release and I'm looking forward to that. I'm not going to be able to say right now if I'll switch to it or not, as it is still quite some time till the next stable relese .
Originally Posted by Kivada
Debian stable package search: https://packages.debian.org/search?s...&keywords=mate
Debian testing package search: https://packages.debian.org/search?s...&keywords=mate
Debian unstable package search: https://packages.debian.org/search?s...&keywords=mate
geolocation services chrash, unity uses eog, evince, gnome terminal, gedit, gnome control center, gvfs,
Originally Posted by omer666
controlled by Gnome morrons... here, i fixed it for you. Gnome is completely destroying Gtk, since Gtk is now not what users need, but what Gnome needs.
Originally Posted by wargames
One only needs to watch planned DEPRECATED features and see that it is time to fork Gtk while there is still time. bunch of widgets that were removed were removed not because people wouldn't use them, but because Gnome didn't use them. same thing is planned for 4.0. now, if anyone needs proof they should just read Cinnamon troubles with Gtk post 3.6
last straw in my head was fitting all default dialogs in Gtk with buttons in title. wtf, can't they do that in Gnome Gtk extension? like destroying really viable desktop was not enough, let's destroy toolkit too
Only sane comment so far
This is by far the only sane comment.
Originally Posted by monraaf
Many of the commenter doesn't even bother to understand what this GeoLocation API is before dumping their non-sense hates.
And for anyone having problem with GNOME 3.10 on Ubuntu, please report it in bug tracker of your distro. BTW only a handful of gnome app are utilizing this API and service now such as Map and World Clock. Thus if Evince or Totem broke, it's very unlikely this API's fault.