The Fork of GNOME2 little by little it is separating from the spawn from which it was created and is becoming a more current and modern Desktop Environment. So we can see it in the official announcement of the release of MATE 1.6.
Note that the changes are not few. In this release, many outdated packages and libraries have been replaced by the new technologies available in GLib. The main improvements are:
Main changes in 1.6 are:
- Support for Systemd-logind.
- Improvements in the side panel of BOX, new framework and support for the new specification of the thumbnails, new dialog of connection to servers and more.
- Panel enhancements: Middle mouse button click to close window can be used, added an option to switch between workspaces with the mouse wheel, and more.
- Improvements in the Window Manager.
- Improvements in Lectern, Calc and other applications.
- Notification daemon improvements.
- Improvements and added support in Gtk2 / Gtk3 themes.
- Icon set improvements.
Anyway. These are just some, if you want to see everything in detail you can reach the official announcement.
MATE 1.6 It is the result of 8 months of intense development and contains 1800 contributions made by 39 people and more than 150 translators.
I used Mate in Sabayon, but it had a lot of Bugs, I used the previous version before this one. One of the things that could not be done I do not know why it was that it was not possible to view the thumbnail views in BOX.
But, let's see when this build is available in sabayon to see what it is, now I'm more than comfortable with Xfce4 😉
Regards!
Does it already include a network manager? When I install it pelao in Debian Wheezy it does not install any and it is not possible to connect to wifi networks. Network-Manager-Gnome is not a solution because it wants to install half a Gnome Shell and with Wicd it is impossible for me to connect to networks with security enabled.
Either way, it will have to be given a chance within a VM.
»Network-Manager-Gnome is not a solution because it wants me to install half Gnome Shell»
A Debian classic 😀
"Wicd is unable to connect to security-enabled networks."
What problem do you have? I connect without problem to WPA / 2 networks.
Did you try the CLI version of NetworkManager?
Wicd just doesn't have the balls to connect me to any kind of wireless network safely. It always hangs when trying to validate the key and eventually throws an error. It does not matter if the network is WEP-WPA / 2. The LCI version is a sloppy solution - in my opinion - because I want it to be a graphical interface. That does not mean that it is against terminal programs. In fact I use several like MC, Moc, Links, Lxsplit, RTorrent, etc. I use a Broadcom 4313 using the broadcom-sta-dkms driver.
If you install it through Synaptic, when you check the packages to install from network-manager-gnome it removes several. There are many that install even if you do an apt-get –no-install-recommends but if you remove it in Synaptic it allows you to continue installing it without many of the required extras (bluez, modemmanager, etc.). It works for me, both the installation and the operation of the manager.
In case there is any doubt, no, Mate 1.6 does not have its own network manager.
Relax my friend that Wicd is still the workhorse of all who do not use DE and want an easy way to connect wirelessly.
What you say attracts my attention because:
1) IF you connect to secure networks
2) Almost nobody has problems with that application.
3) There is nothing similar reported for the latest versions - I didn't search for old versions or Alphas.
In my particular case, I use it on an Ubuntu Server 12.04 LTS that runs on an old notebook and that for some mysterious reason 'drowns' and ends up hanging a wired interface when there is a lot of data traffic.
In this machine I use Wicd to connect to the encrypted Wi-Fi network with a 20-character alphanumeric key and it goes EXCE-LEN-TE.
If it helps you, these are the versions of the installed packages:
[olivetti] j: 0 / etc / cups $ SearchLocal wicd
ii python-wicd 1.7.2.3-1ubuntu0.1 wired and wireless network manager - Python module
ii wicd 1.7.2.3-1ubuntu0.1 wired and wireless network manager - metapackage
ii wicd-curses 1.7.2.3-1ubuntu0.1 wired and wireless network manager - Curses client
ii wicd-daemon 1.7.2.3-1ubuntu0.1 wired and wireless network manager - daemon
ii wicd-gtk 1.7.2.3-1ubuntu0.1 wired and wireless network manager - GTK + client
No, if I am calm. An apology if it seemed otherwise xD
I have always used Wicd, even with KDE. At the moment I am using Ubuntu + Gnome Shell on the laptop while the next Debian Stable appears. And certainly, here Wicd works.
It is also true that there is information on similar problems to connect to the network with Broadcom and Wicd wireless cards, but information from 2 years ago. And although I tried to apply the solutions, I was unsuccessful. A shame.
When installing the gnome network manager with a:
aptitude install network-manager
it doesn't install half Gnome 3.
And the issue of boxed thumbnail views was fixed with a symbolic link:
rm -r $ HOME / .cache / thumbnails
mkdir $ HOME / .cache / thumbnails
cd ~
rm -r .thumbnails /
ln -s ~ / .cache / thumbnails ~ / .thumbnails
and to restart box quickly:
-q box
Excellent, just one point against: those who come from version 1.4 in Debian find it a bit difficult to find the Dconf-editor again since the mateconf-editor is obsolete and does not do anything you tell it to.
Recommendation: improve the migration system so that newer users do not experience any frustration.
The environment at least in Debian Wheezy is robust, stable and the theme and icon pack are really beautiful. Very environment with sustained development.
I like the LXDE desktop better because it is light and the Squeeze distribution, because the stable one gives me more security.
Linux Debian Squeeze LXDE Custom LiveCD on:
http://ricardoliz.blogspot.com
I am in Debian and the Newtwork Manager does not work, when executing nm-applet as root it returns me:
** (nm-applet: 4446): WARNING **: Failed to initialize D-Bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
if I run it as a regular user:
(nm-applet: 4464): Gtk-WARNING **: Theme parsing error: unity.css: 36: 16: Not using units is deprecated. Assuming 'px'.
** Message: applet now removed from the notification area
** Message: applet now embedded in the notification area
🙁
If you could guide me I would appreciate it very much
regards