Call for testing - MATE SlackBuilds

willysr · 06-21-2013, 12:18 AM

The package is built using the latest git version, so you should not get different result

stormtracknole · 06-21-2013, 12:49 AM

Quote:

Originally Posted by willysr

The package is built using the latest git version, so you should not get different result

Ah, good to know. I was just about to try it out.

bonowax · 06-21-2013, 06:19 AM

Successfully installed Mate, but:

When starting X, 'caja' is launched, segfaults and respawns in a loop.

The tty from which I launched X, get filled with lines with the message:

(caja:XXXXX): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed

Scroll locking the tty from which I launched X, allowed to apparently stop the process; launching 'caja' in a terminal window shows the above error message, as well as a message in /var/log/messages:

Jun 21 11:56:45 rapyuta kernel: [ 2048.542711] caja[XXXXX]: segfault at 18 ip 00007fbdc8535c8d sp 00007fffe1e314d0 error 6 in libunique-1.0.so.0.100.6[7fbdc8530000+b000]

willysr · 06-21-2013, 10:00 AM

please show the output of this command

Code:

cat /usr/share/applications/caja.desktop | grep caja

there should be this line: Exec=caja --sync
if not, try to edit the file and add --sync in the Exec=caja line

bonowax · 06-21-2013, 10:28 AM

Here's the output:

Exec=caja --sync
X-MATE-Bugzilla-Product=caja

willysr · 06-21-2013, 10:36 AM

which Slackware version are you using? 14.0 or Current ? 32/64 bit machines?

bonowax · 06-21-2013, 10:39 AM

Slackware 14.0, x86_64, all updates installed with slackpkg.

igadoter · 06-21-2013, 10:46 AM

Hi,

Well I need a precise list of applications created for Window Maker and you are thinking these apps are useful.
I decided to create a functional desktop based on WM cause mu computer is slow. And I cannot get to use Xfce
(no particular reason). I have already installed some apps by slackbuilds - what was listed for "Window maker"
search term at www.slackbuilds.org. wmmixer is fine, wmdrawer is fine - a file manager fsviewer - nice but there
is configuration issue - there are defaults for "View" and "Edit" file commands - say 'mpg123 %s' runs for view
.mp3 file. Well but it doesn't work well if there is a blank in file name - seems 'mpg123 "%s"' fixes this -
but there is a bunch or predefined defaults and fixing this manually is overkill.

Any help and suggestions are very welcomed.

Greetings

Sorry posted in wrong place

chess · 06-21-2013, 12:28 PM

@bonowax, IIRC from your earlier post, you did not do a full install of Slackware, correct? I think you've got something missing which has caused a problem for caja or linbunique.

bonowax · 06-21-2013, 03:23 PM

Indeed, I don't have a full install. I usually leave out things I don't use or that are not required by other packages present, like emacs, tcl and the like. 'l' and 'd' series, however, are fully installed.

I'm considering setting up a virtual Slack environement with a full install and see how it goes.

Thanks

willysr · 06-21-2013, 05:21 PM

i also didn't use a full install for the build machines, but i only left kde, xfce, and e directory while i install the rest

cisneros · 06-21-2013, 07:27 PM

i have several problems with MATE, when i do startx, just a black screen appears nothing else, if i do ctrl+alt+F1, i can see a bunch of errors in the console.
things like:

Code:

couldnt communicate with already running daemon: did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

and

Code:

could not initialize NMClient /org/freedesktop/NetworkManager

and

Code:

GConf Error: Configuration server couldn't be contacted: D-BUS error: Unable to store a value at key '/apps/nm-applet/stamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf

someday i think i ran a program with a gui interface from a "su -" session, while i was already login as a normal user, is that have anything to do with the errors?

i can use the mate-session login as root with no problem, the problem is my normal user.
is there anyway to reset configuration files or something? i have reinstalled mate several times, same result. black screen after startx.
maybe some startup programs that runs with my mate-session of are messed up?

any advice? thanks

chess · 06-21-2013, 10:28 PM

@cisneros -- I've got MATE installed on three stock 14.0 systems and it's running like a top. I've never encountered anything like what you are seeing. Can you provide more detail? What Slackware version? 32 or 64 bit? Full install?

Also, one way to test is to create a second user, log out as your normal user, log in as the new user (who will have a clean $HOME), run xwmconfig and select MATE, and then type 'startx'. If that works, then there is something wonky with your regular user's environment or setup. Maybe running a gui program as root polluted your $HOME, I don't know. Those error messages all seem tied to network manager, not MATE, though. Perhaps you can back up and move certain directories in your regular user's $HOME, such as $HOME/.cache, $HOME/.config, $HOME/.local. Log out and then log back in and try it.

cisneros · 06-21-2013, 10:59 PM

Quote:

Originally Posted by chess

@cisneros -- I've got MATE installed on three stock 14.0 systems and it's running like a top. I've never encountered anything like what you are seeing. Can you provide more detail? What Slackware version? 32 or 64 bit? Full install?

Also, one way to test is to create a second user, log out as your normal user, log in as the new user (who will have a clean $HOME), run xwmconfig and select MATE, and then type 'startx'. If that works, then there is something wonky with your regular user's environment or setup. Maybe running a gui program as root polluted your $HOME, I don't know. Those error messages all seem tied to network manager, not MATE, though. Perhaps you can back up and move certain directories in your regular user's $HOME, such as $HOME/.cache, $HOME/.config, $HOME/.local. Log out and then log back in and try it.

it worked, so what i created a new user to see if mate would run ok, and it did. that gave relieve that the problem was under $HOME, so i renamed .cache to _.cache and so on with others in my old account, and mate now runs ok again.
thanks a lot man.

chess · 06-21-2013, 11:09 PM

@cisneros - glad to hear it! Thanks for testing out MATE SlackBuilds.