SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Mate 1.6 on Current works as advertised. One spot of bother configuring libsku, I usually set LDCONFIG="-L/usr/lib64" and leave the lower-case libs in LIBS. Had to change LIBS="-lgtk" to "-lgtk-3" because I have no gtk in /usr/lib64/pkgconfig, just gtk-2 and gtk-3. I figure things are heading toward GTK+3 anyway, so might as well see what blows up..
Support fot GTK+3 is planned for MATE 1.8, not in current release
Chess: does previous package (without the patch) does have the issue of missing panel on second screen?
If it does, then we can consider this as a bug and i will push this to master
As far as I can recall, GNOME 2 has always kept the panels on the primary screen. I can't see how to put a panel on the external monitor when the laptop screen is on, however. I can right click on the panels on the laptop but that just creates a new panel on that screen. I can't move them over to the external monitor.
I am still having an issue with the screensaver. No matter what I set on the time, it turns on within a few minutes (around 5). I have it set to 20. This is on two different laptops. I'm wondering if I have something in .config that can be overriding it.
@stormtracknole - you're not alone. gnome-screensaver (now mate-screensaver) has always been a bit wonky for me. Glad to hear that other than the screensaver, MATE has been working well for you. It's my daily desktop and has been rock solid and using fairly light resources.
MATE is not a full blown DE such as GNOME or KDE, so it's only focusing on main applications. Third Party applications such as Brasero and GNote will have to installed separately from Mate just like other third party applications listed on SBo Project. Lack of developers working on MATE is another reason why they don't have faster release cycle.
Brasero only requires libunique which is already installed when you build MATE packages from GIT, so all you need is build Brasero using SlackBuild script from SBo or use sbopkg.
I don't know about GNote as it wasn't listed in SBo yet, but if i looked at ArchLinux's GNote package, Slackware-Current already covered all requirements for GNote
Update: GNote requires gtkmm3 from SBo in order to be installed.
I have GNote SlackBuild in my SlackHacks
Last edited by willysr; 06-06-2013 at 06:58 AM.
Reason: Added Gnote SlackBuild script
Back when I was using Mate (maybe a month ago), I was having problems with spontaneous shutdowns. My laptop would just randomly shut down. It wouldn't crash; it would actually initiate the shutdown process (spontaneously) and then complete it.
I have no idea if Mate is the cause, but I stopped getting this after I switched to i3.