How to install a bz2 package?
 

I downloaded some source files in xxxxx.tar.bz2 format.
How would I install a package that is in that format
on slackware?

you should extract the source and compile it yourself. It might be easier to search for this software at SlackBuilds.org for a ready build script that will do this for you:

http://slackbuilds.org/

Actually, this file most likely is not a package, but contains the source code of the SW you want to install. I would suggest extracting it on a directory (ie /usr/src) and then read the README or INSTALL file usually contained in the pack.

I think I tried this and it did not work --> slackpkg install seamonkey.tar.bz2

So I did this (specified current directory) --> slackpkg install ./seamonkey-2.32.tar.bz2



5 minutes of garbage on screen

then please wait for a minute

then 5 minutes of stuff about grep like:
grep: Unmatched [ or [^
grep: Invalid range end
grep: Unmatched [ or [^
grep: Unmatched [ or [^
grep: Unmatched [ or [^
grep: Invalid range end
grep: Unmatched [ or [^
grep: Unmatched [ or [^
grep: Unmatched [ or [^
grep: Unmatched
then 5 minutes of rotating the characters - / | \
so that it looked like a spinning bar.

then 2 minutes of more grep stuff.

then the rotating bar again for minutes

then more alternating grep stuff and rotating bar forever
I finally did a control-C to get aborted the rotating bar
after about 20 minutes.

To my surprise it got installed, and seems to work.

What a puzzling mess!

Slackware comes with seamonkey, if you did a full install.

From where did you get that tar file?

I will check out the slackbuilds.org

Thanks all for the help. I guess the problem is fixed, maybe?

I did the full install, and had seamonkey but it was an older
version, but I wanted an update, because they said there was
some security issues with what I had.

I also uninstalled the older version.

I got the newer from this site:
http://www.seamonkey-project.org/releases/

I downloaded the first one at the top of the page version 2.32

...

do you know how to work with slackpkg, how to install and uninstall packages, pkgtool, etc?

may be we start from here :)

Probably seamonkey was already installed, as Richard Cranium said: it's part of Slackware. That's why you can run it.

You won't find it in slackbuilds.org that ships only packaging material for software not already included in Slackware.

The slackpkg install command is only for Slackware package, and seamonkey.tar.bz2 is not a Slackware package but a source tarball as koloh said, hence the errors.

As previously mentioned it is better to use the Sea Monkey that ships with Slackware. However, if you must have the latest package you could try to use gnashley's utility called src2pkg. His utility takes source files and creates a Slackware package that you can install using the installpkg command. That may work for you.

Src2pkg

Well I guess it is not really fixed. I am using it right now,
but I have to run it as root.

It will not run as a simple user, it gives the following errors when
running it as an ordinary user:

bash-4.2$ seamonkey
1422627568044 addons.manager WARN Application shipped blocklist has an unexpected namespace (http://www.mozilla.org/newlayout/xml/parsererror.xml)
GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
Segmentation fault
bash-4.2$

========================

Before beginning to use src2pkg or similar tools, it would be better that EldonCool learn to use the Slackware tools.

And in this specific cas, Seamonkey 2.32 has already been provided as an upgrade, so the good way to upgrade is:No need to remove the older version first, slackpkg takes care of that.

I checked the release notes, and it says I am running version 2.32 so it is the
current one I installed.

Also I uninstalled the original.

But I still have this problem, that it only runs if I am logged in as root.

I have to get on to other things, will get back to this tomorrow, or later
today.

You have messed your system, the software was not properly installed.

To check, please provide output of following commands:

For most things I just go to a mirror and go into Current and grab the latest version of what I want. So for Sea Monkey I would go to: http://slackware.cs.utah.edu/pub/sla...slackware/xap/ or for 64 bit: http://slackware.cs.utah.edu/pub/sla...ackware64/xap/

And download: seamonkey-2.32-i486-1.txz or seamonkey-2.32-x86_64-1.txz then install it with pkgtool. Sure you could run into an issue where a library needs upgraded or something before the current version will work (haven't seen that yet), but in all these years I have never had an issue getting upgraded versions of software for Slackware right out of current. Quick, simple and flawless. Works for me!

This is a bad advice and furthermore in the OPS's case it is useless as seamonkey-2.32 is already provided for Slackware versions 14.0 and 14.1.

In case someone would like to upgrade a package to a version not provided for one's Slackware version, the right way (not guaranteed to work but a least better) is to download the whole directory in /source for that packages from the file tree of a more recent Slackware version, rebuild the package in the downloaded directory then do an upgradepkg to install the new package, replacing the old.

Why is this bad advice? And I thought he was trying to instal 2.32? I respect your opinion, please explain.

Didier, is what is in source different/newer than the Slackware package in current? Wouldn't you end up with the same thing?

In the case of Seamonkey, the 64bit source is dated January 12 and the Slackware package is dated January 15 so I would think the Slackware package is based on the earlier source package.

I understand that building it for you system is ideal, but if you have a pretty much stock install I'm not sure what the difference is. But I am no expert, just sharing what has worked for me in the past.

It is bad advice, as it can fail because for instance the minimum requested version of some dependency could have been increased to a level not found in the older Slackware version[1]. If that didn't happen to you, you are just lucky.

And yes the OP was trying to install 2.32 in Slackware version 14.0 or 14.1, but for that he could have just either downloaded the new package for his Slackware version and typed "upgradepkg <new_package>", or if he uses slackpkg typed after "slackpkg update" either "slackpkg upgrade <new_package>" or "slackpkg upgrade-all".

[1]To be honest, in that case the build will probably fail anyway when building the package anew (at the configure step), but at least you will know from the inception that there is problem.

Thank you for the explanation Didier, I see what you are saying. I have never used upgradepkg or slackpkg. I get what I need from current like I said or from SlackBuilds. Been using Slackware for 20 years now, back in the day everything was source and you hunted dependencies as needed, I always figured if I ran into an the "minimum requested version of some dependency" issue I would simply go to current and get the necessary updated dependency. I guess I have resisted the upgradepkg and slackpkg tools as it was never a big deal to manage things manually.

Thanks again, maybe I need to explore upgradepkg and slackpkg... :)

(Oh and yes, for those that noticed, I am running FreeBSD on this box, just playing, not giving up Slackware or anything :))

You are welcome Fred. Well, your advice was not intrinsically bad after all, just bear in mind that most people posting questions here are way less experienced than you ;)

Thanks Didier, I hope the OP got/will get it all sorted out in the end! I apologize if I added confusion and took this thread off track.

This is what I have done:

(1) removepkg seamonkey

now it is gone.

(2) slackpkg install seamonkey

It gave me the gui type display that you get
when you install slackware distribution.
I hit return to select this choice: seamonkey-2.32-x86_64_slack14.0.txz
and a block <OK> which I checked, then it installed it with these
messgages:.
So now it is installed, appears to be latest version 2.32, yeah, great!

I type in seamonkey on command line, and it runs, terrific, but
I am still logged in as root, Does it run as ordinary user?

So I exit su, and try as ordinary user:

Nope, this is my result of trying to run as ordinary user:
Also here is this item just done:

So what do you suppose is the problem, that I can't run it as
ordinary user?

Also if we ever figure out why I can't run it as an ordinary user,
I am also wondering why, seamonkey gave me the message that
I should update the browser because this version has security
issues. If I already had version 2.32 then why did I get that
message? I know we really can't answer that, but still that is
what brought on the whole problem.

Searching the error reveals an issue with dconf, but dosen't make sense that it works as root. Maybe try reinstalling it. File is here: http://slackware.cs.utah.edu/pub/sla...0-x86_64-1.txz, you can download it and install with pkgtool...

But maybe try upgradepkg first or removepkg and slackpkg like you did with Seamonkey.

Did you ever open Seamonkey as root while logged in as another user on your DE/WM? If you did, then you could've poluted your configuration files with root owned files, which can cause problems with packages opening up. The only two ways you should open a GUI app as root is 1. if you logged into KDE/XFCE/fluxbox/etc as root, or 2. use a program designed to escalate privilieges in GUI while a regular user is logged in, like kdesu.

If you did run it as root at some point, you can see if you have any files or folders in your home directory that are owned by root.

One more thought.... and I know this sounds wrong for a Linux machine, so don't beat me up... but did you reboot after uninstalling and reinstalling Seamonkey? With your weird issue it might not hurt.

I like bassmadrigal's idea, that sounds possible.

I uninstalled it again,
then installed again,
then exit su
then tried to run it as an ordinary user, same problem.

Also I rebooted and tried to rerun, still same problem.

Did you uninstall/reinstall dconf like I said in a couple posts back? And even more important... did you check into bassmadrigal's suggestion?

Try:

1) removepkg dconf

(2) slackpkg install dconf

EDIT: In hindsight this makes no sense... I was going off the error message you gave that I looked up in Google, listen to Didler below... he is on the right track. [Backing out before I embarrass myself anymore, forgive me, I have been sick all week, which might explain why I am using FreeBSD, or maybe using FreeBSD is making me sick :)]

I suspect that you have some stale files lying around that cause troubles. This can happen when you don't use the proper Slackware tools or the proper packages.

At least this looks weird:as the file names should at least include the version of the removed packages.

So I'm just wondering what can have caused that...

But wait: probably you didn't copy/paste the full output as files not ending with -2* shouldn't be displayed at all by that command.

ls -l /var/log/removed_packages/seamonkey-2*
-rw-r--r-- 1 root root 235653 Sep 12 2013 /var/log/removed_packages/seamonkey-2.12.1-x86_64-1
-rw-r--r-- 1 root root 322441 Jan 30 10:37 /var/log/removed_packages/seamonkey-2.32-x86_64-1_slack14.0



ls -l /var/log/packages/seamonkey-2*
-rw-r--r-- 1 root root 322441 Jan 30 11:49 /var/log/packages/seamonkey-2.32-x86_64-1_slack14.0
bash-4.2$

probably had the file names truncated by the limited screen size somehow,
maybe when I pasted it into my editor.


I did not do anything with dconf, somehow missed that entirely,
what is it?


..

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.

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!