Gxine Stops Working when Upgrading to SeaMonkey 1.1.1

Hi,

After I upgraded the original Slackware Seamonkey package v1.0.5 to v1.1.1 (which I got from Slackware), gxine v0.5.7 stopped working. I found that after I first removed v1.0.5 and then installed v1.1.1 (using pkgtool), v1.1.1 did not create soft links to the library files that gxine needs/uses (eg: libmozjs.so). But, even though I manually soft linked the libs so that gxine would stop complaining, gxine seg faults. Nonetheless, I fell back to seamonkey v1.0.5 and all is dandy once again.

Why is this happening? In what other ways does v1.0.5 impact my system? Does that mean I can't remove/upgrade SeaMonkey without negatively affecting other apps? This sounds odd to me.

I am running Slack 11.0 with kernel v2.6.20.11. If you need more info from me, just let me know.

Dom.

Probably related to this:

Mon May 14 16:39:31 CDT 2007 patches/packages/seamonkey-1.1.1-i486-1_slack11.0.tgz: Upgraded to seamonkey-1.1.1. Removed various symlinks to NSS libraries. If you plan to rebuild the pidgin package in unsupported/pidgin/stable for any reason (you shouldn't need to), first upgrade to this package and then upgradepkg --reinstall the mozilla-nss package.

http://www.slackware.com/changelog/stable.php?cpu=i386

OK, according to the reference provided I should not have to mess with gzine; great!

It then says to reinstall the NSS-package, which I presume means to run upgradepkg --reinstall seamonkey 1.1.1. But would that not just upgrade the libraries? If it does, then I'm back to where I started where gxine seg faults (see original post for details). If it doesn't upgrade the libraries, would that not cause a problem for seamonkey 1.1.1?

Please, do explain.

DPD.

I presume means to run upgradepkg --reinstall seamonkey 1.1.1.

The change log says:

upgradepkg --reinstall the mozilla-nss package

I don't know if what is discussed in the stable changelog is related to your problem, but it sounded similar (i.e. Seamonkey and symbolic links).

Check to see if you have the mozilla-nss package installed and if so reinstall. If you don't know how to do that here is an example:

# cd /var/log/packages
# ls mozilla-nss*
mozilla-nss-$VERSION.tgz
# upgradepkg --reinstall mozilla-nss-$VERSION.tgz

I think you will find mozilla-nss needs to be installed, not reinstalled. I posted a heads-up on this a week or so ago, you can find it by searching this forum for Seamonkey.

Brian

I think there is an issue with gxine after the upgrade, regardless of the mozilla-nss package.

shilo@shilo2:~$ ls -l /var/log/packages/seamonkey-1.1.1-i486-1_slack11.0 
-rw-r--r-- 1 root root 782 2007-05-14 21:58 /var/log/packages/seamonkey-1.1.1-i486-1_slack11.0
shilo@shilo2:~$ ls -l /var/log/packages/mozilla-nss-3.9.2-i486-1_slack11.0 
-rw-r--r-- 1 root root 2730 2007-05-20 03:49 /var/log/packages/mozilla-nss-3.9.2-i486-1_slack11.0
shilo@shilo2:~$ ls -l /var/log/packages/gxine-0.5.7-i486-1                 
-rw-r--r-- 1 root root 3280 2006-12-27 23:00 /var/log/packages/gxine-0.5.7-i486-1
shilo@shilo2:~$ ldd /usr/bin/gxine |grep -i not
        libmozjs.so => not found
shilo@shilo2:~$

Can anyone else verify this?

I found that my system does not have the mozilla-nss* package installed. So, I searched Mozila's web site and found 2 source packages: nss-3.11.5-with-nspr-4.6.5.tar.gz and nss-3.11.5.tar.gz. Which one should I build? Has anyone already built this package? Were there any difficulties or obscure pre/requirements?

Still, building the nss package would be fruitless if this is a bigger issue (as Shilo may be alluding to).

Dom.

shilo@shilo2:~$ ldd /usr/bin/gxine |grep -i not libmozjs.so => not found

This was removed with Seamonkey-1.1.1 upgrade/patch:

# These links just cause problems now...
---snip---
( cd usr/lib
  for file in libmozjs.so libnspr4.so libnss3.so libplc4.so libplds4.so libsmime
3.so libsoftokn3.so libssl3.so ; do
   if [ -L $file ]; then
      rm -f $file
    fi
  done
)

In the stable changelog of Thu Nov 9 18:04:51 CST 2006, Pat said:

"... but meanwhile using firefox-1.5.0.8 with the gxine plugin works just fine. ..."

Originally Posted by ddimuc I found that my system does not have the mozilla-nss* package installed.

It is in /patches/packages

Brian

Originally Posted by shilo I think there is an issue with gxine after the upgrade, regardless of the mozilla-nss package. Can anyone else verify this?

gxine is hosed on my system as well - I tried recreating the symlinks and it still failed.
This goes beyond the mozilla-nss issue as I tried downgrading and that did not work either.

All updates via upgradepkg from local files maintained via rsync (i.e. no swaret etc.)

Well this worked for me - I know it has already been mentioned but can't find exactly where (this thread is getting strung out around the place !!)
As previously stated :

# cd /var/log/packages
# ls mozilla-nss*
mozilla-nss-$VERSION.tgz
# upgradepkg --reinstall mozilla-nss-$VERSION.tgz

... then create a link at /usr/lib/libmozjs.so -> /firefox/libmozjs.so. Everything seems to work now.

Cheers

Sorry to barge in on your thread ddimuc been having similar problems with gxine. BCarey said to take a look at your thread.
bgeddy has written about installing mozilla-nss and creating some links afterwards.
Can bgeddy explain how we should make these links. Not really into all the adding links etc yet.
Many of the members talk about adding links here and there, but forget that for many of us newbies it doesn't mean so much.

As always, appreciate any help that you can give on this matter.

bookie

No problem. Assuming you have a standard setup (the firefox libs are in the right place)- the following will create a symbolic link to "/usr/lib/firefox/libmozjs.so" called "/usr/lib/libmozjs.so". Obviously replace rootpassword with your password !

su -c "ln -s /usr/lib/firefox/libmozjs.so  /usr/lib/libmozjs.so"
Password: rootpassword

See

man - ln

for help with symbolic links. Hope this works for you.

Thanks for being so prompt. Have you any ideas as to which book or books on linux a newbie should begin with? If I had a decent book, then I might learn the command structure and perhaps understand it.
Thanks again for the info.

bookie

Ok - rather than re-iterate what has been done before - this thread has loads of great links for Slackware/General Linux info. I would particularly recommend for general Linux advice the "rute" book - its fantastic. Chapter 15.1 "Soft Links" may be of particular interest to you.

Once you want to cover topics in greater depth, there is "Advanced Bash-Scripting Guide" for bash scripting, "linux kernel in a nutshell" for kernel building etc, all available on - line. (I haven't checked but there will definately be pointers to these in the thread I give you.
Then more specifically for Slackware there is "The Book" - the offical Slackware book at http://www.slackbook.org/ and loads of other useful info out there.

When playing around at the cli (command line interface) - don't forget the "man" command to show manual pages, "apropos" to search the whatis database for strings (this can be very useful), "help" to give help on the shell, "command --help" often gives help for "command".

Forgive me if i am telling you stuff you already know, I am just trying to give generic help. Please don't take my recommendations to be exclusive of any others - there are LOADS of good references on the net for Linux/Slackware.

I think this link should give you a very good starting point. Anyway - have a look here : http://www.linuxquestions.org/questi...d.php?t=546232

Happy reading and good luck in your quest !!

Cya