LinuxQuestions.org - Call for testing

Page 1 of 6

Show 50 post(s) from this thread on one page

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Call for testing - MATE SlackBuilds (https://www.linuxquestions.org/questions/slackware-14/call-for-testing-mate-slackbuilds-4175455139/)

chess

03-22-2013 12:04 PM

Call for testing - MATE SlackBuilds

I've created an initial set of SlackBuild scripts to build and install MATE desktop environment 1.5 (development branch) on Slackware. I'd greatly appreciate testers, suggestions, patches etc.

Screenshots here:
http://mateslackbuilds.github.com/

Github repo:
https://github.com/mateslackbuilds/msb

willysr

03-22-2013 12:15 PM

cloning and start building it :)

Thanks

dugan

03-22-2013 12:27 PM

Did you tell Pat? Remember, he's promised support to whoever starts this project.

chess

03-22-2013 12:30 PM

Thanks willysr - @dugan yes I emailed back and forth w/ Pat about it a few days ago but I'll drop him another email now that I've made it public. Thanks for the reminder. And, I would definitely like this to be a community project so contributors etc. are welcome. Most people around here are a lot smarter than me so I'm sure the scripts will be greatly improved with other people's input. Thanks!

willysr

03-22-2013 12:46 PM

Chess, i think this line caused some minor problem:

Code:

PACKAGE="$(ls -t $TMP/$(ls ${package}*.{xz,bz2,tar.gz} | rev | cut -f2- -d - | rev)-*txz | head -n 1)"

it caused this kind of output
ls: cannot access mate-doc-utils*.bz2: No such file or directory
ls: cannot access mate-doc-utils*.tar.gz: No such file or directory

chess

03-22-2013 12:48 PM

@willysr - yes, it's a harmless error. the script is using the source to determine the package name. Most of the sources are .tar.xz but some are bz2 and others are .tar.gz. Everything installs ok. I'll work on the build script though.

willysr

03-22-2013 12:54 PM

what if you used a wildcard of "*" such as:

Code:

PACKAGE="$(ls -t $TMP/$(ls ${package}*.* | rev | cut -f2- -d - | rev)-*txz | head -n 1)"

ponce

03-22-2013 12:56 PM

I just noticed a minor thing in extra/mate-applets.SlackBuild: at the end it runs a find with some arguments, but the last (mate-invest-applet) is not there, so I changed the find line to avoid interrupting the script

Code:

find $PKG/usr/share/mate/help/$i/* -maxdepth 0 -type d ! -name C -exec rm -rf {} \; || true

EDIT: mate-document-viewer requires mate-keyring.

EDIT2: forgot to say I tried these on slackware64-current.

chess

03-22-2013 01:01 PM

@willysr - yes, I had considered that - just need to make sure it won't accidentally install a package with a partial name, e.g. package-foo and package-foo-bar. But something like that should work.

@ ponce - thanks for that - I'll make that fix.

ponce

03-22-2013 01:09 PM

Quote:

Originally Posted by willysr (Post 4916643)

what if you used a wildcard of "*" such as:

Code:

PACKAGE="$(ls -t $TMP/$(ls ${package}*.* | rev | cut -f2- -d - | rev)-*txz | head -n 1)"

for this seems to me that Pat does

Code:

$PKGNAM-*.tar.?z*

to extract the VERSION fom the sources tarball, like

Code:

VERSION=${VERSION:-$(echo $PKGNAM-*.tar.?z* | rev | cut -f 3- -d . | cut -f 1 -d - | rev)}

maybe can be useful in assembling the package name :)

ponce

03-22-2013 01:31 PM

also mate-power-manager, like mate-document-viewer, needs mate-keyring.

Bazzaah

03-22-2013 01:45 PM

I may well give this a go - I used to like Gnome2.

One question if I may - can you disable tooltips in Mate? Y'know, those annoying little boxes that pop to tell you something obvious? :)

willysr

03-22-2013 01:49 PM

Yes, i think mate-keyring and libmatekeyring should be on extra since it's needed by some modules in extra mentioned by ponce

Myk267

03-22-2013 01:58 PM

Thanks for the this, chess! I installed base and the faenza icon set, and everything's running smooth and fast so far.

Edit: Compiled and installed on Slackware 14, 64 bit!

chess

03-22-2013 02:15 PM

@ponce - I'll change the build script, thanks. Good suggestion. As to mate-keyring, hm, upstream told me that the packages would pick up gnome-keyring which is included in Slackware default. I'll need to look at those compile flags again or move mate-keyring and libmatekeyring back into /base.

chess

03-22-2013 02:28 PM

@Myk267 - great, thanks for letting me know!

chess

03-22-2013 02:46 PM

Ok, moved libmatekeyring and mate-keyring from testing/ to extra/. Might want to disable gnome-keyring* in "Startup Applications" since mate-keyring should handle things.

willysr

03-22-2013 03:01 PM

I think rarian needs to be updated
when building mate-system-monitor, i found this error

Quote:

The file '/usr/share/librarian/Templates/C/scrollkeeper_cl.xml' does not exist.
Please check your ScrollKeeper installation.

while in rarian, i found the file located in /usr/doc/rarian-0.8.1/librarian/Templates/C/scrollkeeper_cl.xml
I guess a simple symlink should fix this problem

Here's the patch i used in order to make it work without adding --disable-scrollkeeper

Code:

diff --git a/base/rarian/rarian.SlackBuild b/base/rarian/rarian.SlackBuild

index 0e6a382..e527598 100644

--- a/base/rarian/rarian.SlackBuild

+++ b/base/rarian/rarian.SlackBuild

@@ -113,8 +113,8 @@ cp -a \

  MAINTAINERS TODO COPYING NEWS README INSTALL COPYING.UTILS COPYING.LIB ChangeLog \

  $PKG/usr/doc/$PRGNAM-$VERSION

 mv $PKG/usr/share/help $PKG/usr/doc/$PRGNAM-$VERSION/help

-mv $PKG/usr/share/librarian $PKG/usr/doc/$PRGNAM-$VERSION/librarian

-rm -r $PKG/usr/share

+(ln -s /usr/share/librarian $PKG/usr/doc/$PRGNAM-$VERSION/librarian)

+

 cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild

 find $PKG/usr/doc/$PRGNAM-$VERSION/ -type f -exec chmod 644 {} \;

 chown -R root:root $PKG/usr/doc/$PRGNAM-$VERSION

chess

03-22-2013 03:04 PM

@willysr - try adding --disable-scrollkeeper \ around line 86 to the autogen.sh configuration. The stuff in /testing is not complete.

willysr

03-22-2013 03:06 PM

on mate-text-editor, you will also have to edit the find code into like this in order to get it built:

Code:

find $PKG/usr/share/mate/help/$PRGNAM/* -maxdepth 0 -type d ! -name C -exec rm -rf {} \; || true

solarfields

03-22-2013 03:16 PM

That's wonderful!
Is a possibility to merge it within SlackBuilds.org considered?

willysr

03-22-2013 03:18 PM

This should make mate-system-monitor build fine

Code:

diff --git a/testing/mate-system-monitor/mate-system-monitor.SlackBuild b/testing/mate-system-monitor/mate-system-monitor.SlackBuild

index bb8f0d0..a113978 100644

--- a/testing/mate-system-monitor/mate-system-monitor.SlackBuild

+++ b/testing/mate-system-monitor/mate-system-monitor.SlackBuild

@@ -92,8 +92,8 @@ make install DESTDIR=$PKG

 find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" | grep ELF \

  | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true

 

-find $PKG/usr/man -type f -exec gzip -9 {} \;

-for i in $( find $PKG/usr/man -type l ) ; do ln -s $( readlink $i ).gz $i.gz ; rm $i ; done

+#find $PKG/usr/man -type f -exec gzip -9 {} \;

+#for i in $( find $PKG/usr/man -type l ) ; do ln -s $( readlink $i ).gz $i.gz ; rm $i ; done

 

 # Remove perllocal.pod and other special files that don't need to be installed,

 # as they will overwrite what's already on the system.  If this is not needed,

chess

03-22-2013 03:22 PM

@willysr - thanks - I will actually replace that with the code I've used in the other slackbuilds which is an if/then block to look for $PKG/usr/man. I just haven't been focusing on testing/.

willysr

03-22-2013 03:27 PM

@Chess:
could you have a look on the rarian changes i made above?
That should make mate-system-monitor built fine here as long as you apply the patch for mate-system-monitor as well

willysr

03-22-2013 03:28 PM

my approach will be making sure all of the base,extra, and testing packages gets built and when it's done, i can test them all at once :)

chess

03-22-2013 03:34 PM

@willysr - I think I got all your changes but let me know if I missed something. Thanks!

willysr

03-22-2013 03:36 PM

Basically you don't need to compress man for mate-system-monitor as it doesn't have any manual page :)

willysr

03-22-2013 03:37 PM

OK, i will rebuilt all of them right now and go to sleep... it's 3.37 AM here :)
i will see the results tomorrow

Thanks Chess

chess

03-22-2013 03:38 PM

Yeah, I know, a lot of them don't but I like that code just in case a man page is ever added. ;-)

Edit - thanks willysr and g'nite!

comfree

03-22-2013 04:02 PM

Works perfekt on a fresh installed Slackware-64 14.0.

I will not use the MATE desktop, but thanks for your work!

willysr

03-22-2013 08:53 PM

On my machine, it worked well, but it started a lot of file manager processes, causing the systray no room for other application and causing the machine to work on high load all the time until i logged out of the system.

any ideas on how to solve this problem?

i'm running -Current and i have all modules built fine here

willysr

03-22-2013 09:09 PM

i traced the mate-file-manager and run it in KDE and it reported an error

Code:

willysr@desktop:~$ caja

Initializing caja-open-terminal extension

The program 'caja' received an X Window System error.

This probably reflects a bug in the program.

The error was 'BadDrawable (invalid Pixmap or Window parameter)'.

  (Details: serial 7 error_code 9 request_code 53 minor_code 0)

  (Note to programmers: normally, X errors are reported asynchronously;

  that is, you will receive the error a while after causing it.

  To debug your program, run it with the --sync command line

  option to change this behavior. You can then get a meaningful

  backtrace from your debugger if you break on the gdk_x_error() function.)

however, when i ran caja --sync as suggested, it worked well...
now the problem is how to make caja is called with --sync parameter by default :)

chess

03-22-2013 09:14 PM

Huh, I'm not seeing that at all. It's working nicely here, 136 processes total with no real load. How are you starting MATE - from KDM/login manager or via startx?

willysr

03-23-2013 02:45 AM

Via startx after i changed the default DE into mate

willysr

03-23-2013 07:31 AM

i solved it temporarily by removing mate-file-manager-open-terminal and mate-file-manager

fskmh

03-23-2013 07:57 AM

First off - thanks for your efforts with this Chess.

I did a git clone, ran base/mate-build-base.sh and it fell over when it got to gtk-engines with "
You must have automake 1.7.x installed to compile".

So I replaced ./autogen.sh in the SlackBuild with ./configure and it got through the configure process and built. I realise this is probably not as robust but I'm curious to see what Mate looks like.

I am building on slackware64-current (March 20) BTW.

The rest of base and extra was uneventful. I pushed my luck and went into testing as well, and I have a few comments:

(1) mate-screensaver - the SlackBuild needed the old -L/usr/lib64 trick in

Code:

elif [ "$ARCH" = "x86_64" ]; then

  SLKCFLAGS="-O2 -fPIC -L/usr/lib64"

  LIBDIRSUFFIX="64"

(2) mate-system-monitor required me to first install libgtop.
(3) mate-text-editor required me to first install gtksourceview.

Just logged out of KDE and logged into Mate desktop without rebooting and everything seems to be working.

I spoke too soon. When I launch mate-terminal I get this:

Code:

fskmh@workstation:~> mate-terminal 



(mate-terminal:3356): GLib-GIO-ERROR **: Settings schema 'org.gnome.system.proxy.http' does not contain a key named 'use-http-proxy'

Trace/breakpoint trap

I am explicitly using a proxy (Squid). If I go into "Control Center" and then "Network Proxy" and change to "Direct internet connection", mate-terminal launches fine. Perhaps this is an upstream problem though, because there is no matching key in that schema:

Code:

fskmh@workstation:~> gsettings list-keys org.gnome.system.proxy.http

authentication-password

authentication-user

enabled

host

port

use-authentication

Tried the following and I can confirm that it does not work:

Code:

fskmh@workstation:~> gconftool-2 --set /system/http_proxy/use_http_proxy --type bool true

fskmh@workstation:~> gsettings set org.gnome.system.proxy.http host '127.0.0.1'

fskmh@workstation:~> gsettings set org.gnome.system.proxy.http port 3128      

fskmh@workstation:~> gsettings set org.gnome.system.proxy mode 'manual'

I suspect that something has to be recompiled with this key enabled.

chess

03-23-2013 10:57 AM

Quote:

Originally Posted by fskmh (Post 4917068)

First off - thanks for your efforts with this Chess.

Thanks for testing!

Quote:

I did a git clone, ran base/mate-build-base.sh and it fell over when it got to gtk-engines with "
You must have automake 1.7.x installed to compile".

Yes, I have to assume that folks are building on a full install but thanks for letting me know how to proceed without automake.

Quote:

The rest of base and extra was uneventful. I pushed my luck and went into testing as well, and I have a few comments:

(1) mate-screensaver - the SlackBuild needed the old -L/usr/lib64 trick in

Code:

elif [ "$ARCH" = "x86_64" ]; then

  SLKCFLAGS="-O2 -fPIC -L/usr/lib64"

  LIBDIRSUFFIX="64"

Hmm, thanks - I'll check into this.

Quote:

(2) mate-system-monitor required me to first install libgtop.
(3) mate-text-editor required me to first install gtksourceview.

Yes, those dependencies should already be listed in the READMEs. The stuff in /testing, BTW, is not supported -- that's why they are in /testing. :-) I might add those deps or might not.

Quote:

Just logged out of KDE and logged into Mate desktop without rebooting and everything seems to be working.

I spoke too soon. When I launch mate-terminal I get this:

Code:

fskmh@workstation:~> mate-terminal 



(mate-terminal:3356): GLib-GIO-ERROR **: Settings schema 'org.gnome.system.proxy.http' does not contain a key named 'use-http-proxy'

Trace/breakpoint trap

Code:

fskmh@workstation:~> gsettings list-keys org.gnome.system.proxy.http

authentication-password

authentication-user

enabled

host

port

use-authentication

Tried the following and I can confirm that it does not work:

Code:

fskmh@workstation:~> gconftool-2 --set /system/http_proxy/use_http_proxy --type bool true

fskmh@workstation:~> gsettings set org.gnome.system.proxy.http host '127.0.0.1'

fskmh@workstation:~> gsettings set org.gnome.system.proxy.http port 3128      

fskmh@workstation:~> gsettings set org.gnome.system.proxy mode 'manual'

I suspect that something has to be recompiled with this key enabled.

Hmm, I have not seen these issues at all and I've now installed this on three separate systems, one running 64 bit current, but then again I don't use squid. Thanks for letting me about the fix in this particular use case.

I appreciate the testing and feedback!

willysr

03-23-2013 11:47 AM

i can confirm that everything is working well on Slackware64-Current with only base packages installed (no extra and testing)
now testing in another Slackware-Current machine with only base package installed

if it's proven to be OK, then i guess one of the modules in extra/testing caused the problem i had with file-manager in base

chess

03-23-2013 02:07 PM

Quote:

Originally Posted by fskmh (Post 4917068)

F
(1) mate-screensaver - the SlackBuild needed the old -L/usr/lib64 trick in

Code:

elif [ "$ARCH" = "x86_64" ]; then

  SLKCFLAGS="-O2 -fPIC -L/usr/lib64"

  LIBDIRSUFFIX="64"

Following up on this -- mate-screensaver built and installed fine on my slackware64-14.0 and slackware64-current systems and chroots without this change and I see that mate-screensaver.pc was correctly installed into /usr/lib64, so not sure why we would need to add this. What happened on your system when you tried to build it?

fskmh

03-23-2013 03:23 PM

Here is what I get after running the build script in an "su -l" environment (without the -L/usr/lib64 kludge):

Code:

..

..

make[3]: Entering directory `/tmp/msb/mate-screensaver-1.5.2/src'

  CCLD    mate-screensaver-gl-helper

/usr/lib64/gcc/x86_64-slackware-linux/4.7.2/../../../../x86_64-slackware-linux/bin/ld: skipping incompatible /usr/X11R6/lib/libbz2.so when searching for -lbz2

/usr/lib64/gcc/x86_64-slackware-linux/4.7.2/../../../../x86_64-slackware-linux/bin/ld: skipping incompatible /usr/X11R6/lib/libbz2.a when searching for -lbz2

/usr/lib64/gcc/x86_64-slackware-linux/4.7.2/../../../../x86_64-slackware-linux/bin/ld: skipping incompatible /usr/X11R6/lib/libz.so when searching for -lz

/usr/lib64/gcc/x86_64-slackware-linux/4.7.2/../../../../x86_64-slackware-linux/bin/ld: skipping incompatible /usr/X11R6/lib/libz.a when searching for -lz

/usr/lib64/gcc/x86_64-slackware-linux/4.7.2/../../../../x86_64-slackware-linux/bin/ld: skipping incompatible /usr/X11R6/lib/libresolv.so when searching for -lresolv

/usr/lib64/gcc/x86_64-slackware-linux/4.7.2/../../../../x86_64-slackware-linux/bin/ld: skipping incompatible /usr/X11R6/lib/libresolv.a when searching for -lresolv

/usr/lib64/gcc/x86_64-slackware-linux/4.7.2/../../../../x86_64-slackware-linux/bin/ld: skipping incompatible /usr/X11R6/lib/libpthread.so when searching for -lpthread

/usr/lib64/gcc/x86_64-slackware-linux/4.7.2/../../../../x86_64-slackware-linux/bin/ld: skipping incompatible /usr/X11R6/lib/libpthread.a when searching for -lpthread

/usr/lib64/gcc/x86_64-slackware-linux/4.7.2/../../../../x86_64-slackware-linux/bin/ld: skipping incompatible /usr/X11R6/lib/librt.so when searching for -lrt

/usr/lib64/gcc/x86_64-slackware-linux/4.7.2/../../../../x86_64-slackware-linux/bin/ld: skipping incompatible /usr/X11R6/lib/librt.a when searching for -lrt

/usr/lib/libXext.so: could not read symbols: File in wrong format

collect2: error: ld returned 1 exit status

make[3]: *** [mate-screensaver-gl-helper] Error 1

make[3]: Leaving directory `/tmp/msb/mate-screensaver-1.5.2/src'

make[2]: *** [all] Error 2

make[2]: Leaving directory `/tmp/msb/mate-screensaver-1.5.2/src'

make[1]: *** [all-recursive] Error 1

make[1]: Leaving directory `/tmp/msb/mate-screensaver-1.5.2'

make: *** [all] Error 2

I have experienced the linker trying link a 32 bit library with the odd package I have compiled in the past so I usually just force it to use /usr/lib64 without batting an eyelid.

I must confess - this is on slack64-current with a truckload of extra packages (mostly from SBo).

P.S. I have updated the following packages in the meantime:
mate-calc-1.5.2
mate-control-center-1.5.5
mate-desktop-1.5.8
mate-icon-theme-faenza-1.5.1
mate-keyring-1.5.1
mate-media-1.5.2
mate-settings-daemon-1.5.7
mate-terminal-1.5.1
mate-themes-1.5.1
mate-window-manager-1.5.5

These I added myself:
mate-file-manager-gksu-1.5.0
mate-bluetooth-1.5.1
mate-sensors-applet-1.5.2
mate-netspeed-1.5.2

I've been using this desktop for most of the afternoon and nothing's fallen over so far. Pulseaudio also seems to work the same as it does in KDE.

ponce

03-23-2013 03:30 PM

Quote:

Originally Posted by fskmh (Post 4917340)

I have experienced the linker trying link a 32 bit library with the odd package I have compiled in the past so I usually just force it to use /usr/lib64 without batting an eyelid.

this is because you are using a multilib environment, that usually is not supported by *.SlackBuild scripts.

fskmh

03-23-2013 03:37 PM

Ah, thanks ponce - I suspected as much.

fskmh

03-23-2013 07:43 PM

Just experienced the same issue willysr mentioned in #31. I tailed ~/.xsession-errors and got a bunch of these:

Code:

** Message: Initializing gksu extension...

Initializing caja-open-terminal extension

The program 'caja' received an X Window System error.

This probably reflects a bug in the program.

The error was 'BadDrawable (invalid Pixmap or Window parameter)'.

  (Details: serial 7 error_code 9 request_code 53 minor_code 0)

  (Note to programmers: normally, X errors are reported asynchronously;

  that is, you will receive the error a while after causing it.

  To debug your program, run it with the --sync command line

  option to change this behavior. You can then get a meaningful

  backtrace from your debugger if you break on the gdk_x_error() function.)

While I was fiddling around looking for more details it stopped by itself after about a minute. Looks like it stopped because X reached its limit on the number of client connections.

P.S. I am using runlevel 4 + KDM.

chess

03-23-2013 07:48 PM

Try removing the mate-file-manager-open-terminal package and see if that helps. Willysr removed it and the problem cleared up apparently

I can't reproduce it here -- the file manager and the open-terminal extension work fine.

fskmh

03-23-2013 08:03 PM

Quote:

Originally Posted by chess (Post 4917443)

That was the first thing I tried - didn't help.
Tried disabling compositing as well, but that didn't help either.

What did help was editing /usr/share/applications/caja.desktop and changing "Exec=caja" to "Exec=caja --sync".

chess

03-23-2013 08:08 PM

Can you provide more detail on what you were doing when this happens or find a way to reproduce?

Edit: it also looks like you are running the gksu extension? I have not built that yet. You might want to remove that too to see if it helps.

fskmh

03-23-2013 09:11 PM

So I removed mate-file-manager, as well as the open-terminal extension and the gksu extension that I added and the problem went away, just as willysr said in #35.
I then reinstalled just mate-file-manager, rebooted and the problem came back.

I've tried looking around in ~/.mateconf, ~/.config/caja and ~/.local/share/applications for any kind of cached metadata that I can delete but no luck there. I have reinstalled mate-file-manager and both extensions so I can fiddle around some more.

chess

03-23-2013 09:16 PM

Try clearing out ~/.config/caja. I'm checking with MATE upstream in IRC and looking through the Caja bug reports but not able to find anything just yet. I wish I could reproduce. I've been using MATE and Caja for the past week while building these scripts and have never run into this problem. :/ Thanks for helping to try and track this down.

willysr

03-23-2013 09:16 PM

Quote:

Originally Posted by chess (Post 4917443)

I think this is 32-bit spesific issue and only happened when the underlying system is quite 'polluted' with other DE's config file

I tested on pure Slackware-Current machine on VM and it worked fine there, but it does happened on my main machine in which i have KDE, XFCE, E17, and Mate DE installed

willysr

03-23-2013 09:19 PM

Chess, for the meantime, is it OK with the suggested solution? adding --sync in the mate-file-manager .desktop file?

All times are GMT -5. The time now is 09:47 AM.

Page 1 of 6

Last »

Show 50 post(s) from this thread on one page