dconf is a library.. if you Google the error you provided "GLib-GIO-Message: Using the 'memory' GSettings backend." you will see this error comes up a lot. Not real sure how it applies in your situation.

From what I read an uninstall and reinstall of dconf might fix the issue. Don't think it will hurt... I ran the commands I suggested on my box and it uninstalled and reinstalled without issue. Makes no sense since Seamonkey works as root, but might be worth a try.

Do at your own risk!

1) removepkg dconf

(2) slackpkg install dconf

And reboot.

Woke up thinking about this, yeah I have no life.... as was mentioned earlier, it could be some stale corrupt files hanging around in your user account. Try creating a new non root user and see if Seamonkey works with that user.

1 members found this post helpful.

That struck me as a rather brilliant idea, so I tried it.
It worked, but was not easy, because I had to go through
the stuff of getting a wifi connection with the new user
and that took about half an hour, finding wifi passwords etc.

So, I am on seamonkey right now as a new user ID.

Now I wonder just how much trouble it might be to find
what was causing the problem in my old user login.
Any ideas what files might possibly be the culprit?

I got to thinking about this more with your idea to make a new
user, and get rid of the files that were probably the problem
by having them rebuilt from scratch by a new user. My thinking
was that it must be that seamonkey builds its needed directories
and files when it first initializes. When else could it do it?

The programs for adding new users are not going to know anything
about seamonkey files, so seamonkey must take care of its own
files.

Therefore I thought why not just delete those seamonkey files
in my offending user that can't run seamonkey and let it rebuild
them, after all it must be built into the program to build them
if they are not there, who else could keep track of seamonkey
files?

So I found a directory in my user area "joe" and it was this:

/home/joe/.mozilla/seamonkey/

I deleted everything in that directory.

Problem solved, seamonkey then ran and I am on it now.

It'd probably be a good idea to run what I suggested in my previous post. If you did run seamonkey as root at some point while logged in as your normal user, other files outside of ~/.mozilla/seamonkey might be affected and could cause issues with other programs.

http://www.linuxquestions.org/questi...ml#post5309060

In the future, if you need to run a program as root while logged in as another user, use kdesu PROGRAM_NAME. This will prevent root owned files from cluttering your home directory.

I gave that a try:
Worked pretty good, like you said. I was not sure since
it appears to be a kde prrogram, and I am not using kde,
but it worked okay, like you said, after asking me for
root password.

Sweet! Glad you got it figured out!