Call for Testers: Comparison of MATE 1.14 (mix build vs fully GTK+3 build)
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.
Yes, most of the majors are now fixed already, but there are some "SHOULD HAVE" issues on the list.
plugin support in pluma will likely be removed unless they find a real fix for this issue in the future for GTK+3 build.
It takes quite a bit of stress to crash the applets on the mate-panel. I had to run x11perf to stress test the VM and had to continuously check/uncheck the box to enable/disable the compositor for the applets to crash. Still, mate relaunches the crashed applets and you can continue on working.
That is too bad about plugin support in pluma. Hopefully upstream can fix it.
But not every i586 user can, specially those using old machines.
Well, I just installed SlackMATE on a single core 64 bit VM with 1024 MB RAM and rebuilt mate-1.12. It took 17 minutes. So I can estimate that on some piece of junk that is still able to turn on, it will take about an hour to build MATE and its several dependencies.
Some notes on compiling MATE-GTK3 for newbies like me.
I checked out the slackbuilds and compiled on a fresh 32 bit current install with the kde/kdei/xfce package sets NOT installed. I used the following commands...
Code:
$ git clone https://github.com/mateslackbuilds/msb.git
$ cd msb
$ git pull
$ git checkout GTK3
$ su -
# cd /home/keith/msb
# ./mate-build-deps.sh && ./mate-build-base.sh && ./mate-build-extra.sh
...and about 90 mins later I had my MATE desktop. This is on a Thinkpad X61s with 1Gb RAM and both cores running but with 'balanced' option set in BIOS, and an active Internet connection for the source file and dependency downloads. I have a single large / directory so no problems with space on /tmp.
The script installs each package as it is compiled. The packages are left in /tmp. I've copied all the *msb.txz files from /tmp to ~/msb-pkg and there are 52 of them adding up to about 102Mb according to Caja. The /tmp/msb folder where the source is unpacked shows around 1.3Gb of space in use.
I'm wondering if there is an option to the scripts to build a nicely organised binary set like on slackware.uk/msb without installing as you go?
Last edited by keithpeter; 05-08-2016 at 08:08 AM.
Thanks for the plug but slackrepo probably won't build the new msb successfully out of the box yet I was going to try that this weekend, but seem to have been sidetracked by the mega haskell breakage in SBo master ... I'll drop a note here if I get round to it.
I'm wondering if there is an option to the scripts to build a nicely organised binary set like on slackware.uk/msb without installing as you go?
At this moment, no
That's because this organization is not permanent and it's based on our preferences
we use base to denote basic packages to get MATE running with additional packages for daily usage such as graphic viewer, file manager, and terminal.
extra is meant for extra applications that upstream provided, not mandatory, but nice to have
this can changed in the future so i don't have plan to add the output path in the SlackBuild itself
Thanks for the plug but slackrepo probably won't build the new msb successfully out of the box yet I was going to try that this weekend, but seem to have been sidetracked by the mega haskell breakage in SBo master ... I'll drop a note here if I get round to it.
I just used the slackpkg clean-system command to remove the MATE desktop, then rebooted and reinstalled from the packages I copied out of /tmp using installpkg, using xwmconfig to select the mate-desktop-session.
Not especially elegant but it works. Grab the tar file for the 32 bit packages compiled against current updated to today from here...
At this moment, no
That's because this organization is not permanent and it's based on our preferences
we use base to denote basic packages to get MATE running with additional packages for daily usage such as graphic viewer, file manager, and terminal.
extra is meant for extra applications that upstream provided, not mandatory, but nice to have
this can changed in the future so i don't have plan to add the output path in the SlackBuild itself
I remember some time ago i added another variable to the build script, TMP and OUTPUT which can be used to set where do you want to place the temporary build directory and output directory.
You can try to run the scripts like this for each build script if you want to have separate output directory
Code:
OUTPUT=/tmp/base sh ./mate-build-base.sh && OUTPUT=/tmp/extra sh ./mate-build-extra.sh
Running on Slack64 Current Multilib XFCE with the Clearlooks-Phenix v6 (which is advertised for GTK 3.14 and plays nice with Firefox 46) I compared Caja, Atril, Engrampa and Pluma from your testing/1.14 and testing/1.14-gtk3 builds. I experienced no crashes or the like.
With GTK3 Caja's line spacing is wider (a full height window displays 35 lines as compared to 38 with GTK2) and the "zebra" background effect is gone.
With GTK3 Pluma displays 67 lines as compared to the 68 with GTK2, so that difference is negligible.
The "zebra" background effect is mentioned in the known bugs list, but for as far as I can see Caja's wider linespacing is not.
Regards, Dick
for Caja's wider linespacing, if you think it's worthed to be reported, please do so in their Github issue tracker in order to be processed by upstream.
Thanks for the plug but slackrepo probably won't build the new msb successfully out of the box yet I was going to try that this weekend, but seem to have been sidetracked by the mega haskell breakage in SBo master ... I'll drop a note here if I get round to it.
Good to know. Sorry to all for the misinformation!
I saw that a 'slackrepo_msb.conf' configuration file existed in the latest git of Slackrepo but haven't tried it yet. It points to willy's mateslackbuilds/msb repo on github, so I guess that is where the confusion comes in.
for Caja's wider linespacing, if you think it's worthed to be reported
I did some further testing and found that with the Adwaita theme the wider line spacing does not occur. So it is a Clearlooks-Phenix problem, not a Caja one.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.