SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Yesterday's update has pushed Slackware's GTK+3 stack to 3.22.12 along with other changes, but what's critical to MATE is GTK+3's version. Since MATE is based on GTK+3 and every GTK+3 release bring changes to the behaviour and appearance, running MATE built from an earlier GTK+3 version on top of different GTK+3 version built against it may cause some issues.
As -current divert more and more from -stable, it's probably time for master branch of MSB project to move forward to keep up with -current development. For stable releases will be handled by 14.2-mate-1.18 as usual.
For those running current, i have updated some scripts to compile the latest version based on latest GTK+3 stack on -current. You might want to upgrade mate-themes to match GTK+3 version and also caja, although it's recommended to rebuilt everything.
I have rebuilt every MATE packages for -current and pushed it in the usual playground. Please note that you need to remove vte3 as -current has upgraded vte to 0.44.3. If you are interested to see the changes, please have a look on GitHub.
Don't forget to log out and log in again after upgrading for caja to use the new code linked against GTK+3 3.22.12.
you can try it on VM first and if you are satisfied, you can migrate in your bare metal
Yea, I'm moving my build and test rigs to current now. I just fired up XFCE on current and man does it look good. I'll be playing with MATE and building Cinnamon on it soon!! What a difference!
Skaendo: I have pushed the changes in master branch for CSB as well, but i haven't tested them on clean VM yet.
I just tested it locally on my desktop and seems to be OK so far.
Skaendo: I have pushed the changes in master branch for CSB as well, but i haven't tested them on clean VM yet.
I just tested it locally on my desktop and seems to be OK so far.
Sweet, I'll check it out this weekend.
I was hoping that I could get your input on something slightly unrelated, I'm trying to build "mint-mdm" (MDM Display manager), I can get it to compile and work fine, but it is screwing with gksu. I'm not sure but I think that it might have something to do with pkexec? gksu works from a terminal, but not from like nemo.
Unfortunately it requires webkitgtk, so it's kind of a pain. Also, it needs to be built without csb's pam on the system or else it will not work.
I think not all themes are ported to GTK 3.22 as they are based in Linux Mint usage which is still based on GTK 3.18
That is my thought as well. The Mint-X-Themes in my repo act the same, but I'm getting transparent borders and controls as well. I really hope that they port the X-Themes when they finally do upgrade GTK+ to 3.22+.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.