Call for testing - MATE SlackBuilds

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

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.

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?

fskmh · 03-23-2013, 09:22 PM

Quote:

Originally Posted by willysr

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

I have all of those installed as well.

willysr · 03-23-2013, 09:35 PM

i have a new problem here
the mouse cursor is not visible on the desktop, but probably it's caused by the polluted machine i had, because it didn't happen on 32/64 bit machine on VM

still finding the source problem and it's getting harder since i used the buggy NVidia 304.84 driver which unables me to see the XOrg's error message on tty

chess · 03-23-2013, 09:42 PM

@willysr - I can't find any documentation on what the --sync option does. It doesn't appear in the man page or when caja is run with --help. Any ideas? I mean, I see the error message that says to use it but what does it do? As to your cursor problem, I'm afraid I'm not seeing that either. And what do you mean by "still finding the source problem" - you mean the Caja --sync message?

willysr · 03-23-2013, 09:46 PM

i think that option is used when you want to debug your system, since it will give more information when you traced it using gdb

here's the quote when i tried to run caja without --sync

Quote:

willysr@desktop:~/msb/base/mate-file-manager$ caja
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.)

the --sync parameter is safe to be used, but it will give additional message when something goes wrong

---------- Post added 24-03-13 at 09:47 ----------

Quote:

Originally Posted by chess

@willysr - I can't find any documentation on what the --sync option does. It doesn't appear in the man page or when caja is run with --help. Any ideas? I mean, I see the error message that says to use it but what does it do? As to your cursor problem, I'm afraid I'm not seeing that either. And what do you mean by "still finding the source problem" - you mean the Caja --sync message?

source problem of the missing cursor

willysr · 03-23-2013, 11:00 PM

i finally solved most of the problems (probably all, not sure about new bugs) by clearing this directory
$HOME/.local
$HOME/.config
$HOME/.cache

you might want to make a backup on these directories first

chess · 03-23-2013, 11:21 PM

Quote:

Originally Posted by willysr

i finally solved most of the problems (probably all, not sure about new bugs) by clearing this directory
$HOME/.local
$HOME/.config
$HOME/.cache

you might want to make a backup on these directories first

Yes, I think this is why clean installs appear to have no major issues while installs on existing setups can seem wonky. These directories have various config files, caches, and other bits that can cause problems.

clod89 · 03-25-2013, 05:06 PM

Just in case someone wanted the pre-built packages I found these from salix:

Mate 1.4: ftp://slackware.org.uk/salix/x86_64/14.0/salix/mate/

Mate 1.5 (development version for 1.6, packages for 1.6 will likely be uploaded too from what I understand):

http://people.salixos.org/gapan/mate_1.5_for_slack14.0/

I still have to try them myself so I can't vouch for the quality but hopefully at least with 1.4 version there shouldn't be major issues.

fskmh · 03-25-2013, 05:39 PM

I suspect the upgrade to glib2-2.34 (from glib2-2.32) on March 23 broke some things.
I decided to recompile base and libunique failed with some messages about "'g_value_array_get_nth' is deprecated". Some details here - https://developer.gnome.org/gobject/...ue-arrays.html

As a workaround to get libunique to compile I added "-Wno-deprecated-declarations" to the compiler flags. After I've recompiled and reinstalled base I will try and fire up MATE-desktop again.

EDIT: Nope, MATE-desktop still starts up without the panel.

chess · 03-25-2013, 06:07 PM

@fskmh - please pull latest from git. The libunique fix was committed already. Willysr and I are running MATE without issues on Slackware 14 and -current. Everything builds and compiles fine on stock installs.

fskmh · 03-25-2013, 06:18 PM

Ooops, thanks I will do a git pull now.