Hi, Installed Slackware 14.2 32bit
Then per this link I installed Wireshark w/oany visible issues. But when I ran wireshark-gtk I got this weird message:

What else do I need to install now and how? Sorry for possible newbie question.

Welcome to LQ Slackware forum

See https://www.linuxquestions.org/questions/slackware-14/nixnote-requires-tidy-which-package-is-this-4175623199t/#post5816541
There is wireshark at SBo for 14.2 https://slackbuilds.org/

Just saw the 'uname -a' output and seems you didin't update.
You have to choose a mirror in /etc/slackpkg/mirrors (for 14.2)
and run as root

1 members found this post helpful.

you don't need to clean your system unless you want to un-install every 3rd party install you have or black list, or slackpkg clean-system, then un-select everything you do not want deleted off of your system .

or try installing portaudio
for stable
https://slackbuilds.org/repository/1...ent/portaudio/


Ponce slackbuilds are for current, if you have current that slack build may still work.

Linux slackwhere101 4.4.118 thats stable kernel, so yeah, maybe you for got a dep or 2 before you installed WireShark.

I have to admit I have no idea how slackbuilds is set up for 32bit, if it is even... so yeah... still .. maybe you forgot a dep or 2 before you installed WireShark.

1 members found this post helpful.

Not in this case. This is from his packages for 14.2. If you look at the URL, you will see that.

@OP, pkgs.net is a horrible site to use with Slackware packages. It doesn't really provide you the information you need to be able to properly install packages. It also makes it really easy to mix packages from different repos, which can have some bad effects on your system.

In this case, pkgs.net doesn't tell you that wireshark has dependencies. Also, ponce doesn't provide anything separate stating what dependencies are required and has this caveat on his README:

In this case, the mandatory dependencies for wireshark from SBo are:

However, according to ponce's README from above, there could also be optional dependencies that are included as well.

As is hopefully now obvious based on your error message and the above info, ponce included *at least* the portaudio optional dependency. So, at a minimum, you will need to install that along with all the required dependencies listed above. If you try and start it and it errors out again, you'd need to look at the other optional dependencies and install any of those that may be needed.

This is why it is typically recommended to build things yourself using the scripts on SBo. Once you're familiar with the process, then it is nice to add in some of the automated tools that can help minimize the difficulties that can arise from programs that have a lot of dependencies.

Hi senglory, welcome to LQ.

you shouldn't use pkgs.org for your packages need, that is a site full of ads and not related to Slackware in any way that mixes different packages sources, creating messes on the systems of people that use it.
the asshole guy managing the site has added my repository without asking me anything, so that people downloading my packages from pkgs.org can't read the README (in short, there's no dependency resolution of any kind).
if you want to install *just* wireshark your best option, IMHO, is to do it via SlackBuilds.org (installing all of its dependencies first).
IMHO, if you will keep using pkgs.org you really should ask for help there...

P.S. bassmadrigal has been faster!
to clarify, my package *does not* use just the three above.

1 members found this post helpful.

I missed that link. The one he installed much then have been build to use portaudio, that too would be a reason for it to do as it is doing.

he too could go back and find portaudio as i suggested and install that. giving wireshark what it wants, feeding the shark will make it happy, then it should work.

Or download source or Ponce's off of his sight and build it they way OP wants it.

You've already gave him the list to work off of.

(I've grabbed a few things off of there before and never had an issue with them, but now that *you* point that out, their really isn't anything informing someone of the validity of what they have. If they are mirroring off of someone else sight or building it themselves, especially Slackware because 3rd party needs to be built separately. Whereas all of the other stuff is in the dostro's repo, ie debian etc.)

it might just be someone trying to help out that is legit to the point of I just mirror this stuff point of contact and using a free web sight to do it on. Hence the advertisements.

https://slackware.pkgs.org/

ok, how can I install PORTAUDIO from this site?

download
both files un tar the portaudio.tar.gz then put the other one inside of that directory.

chmod +x portaudio.SlackBuild
sudo ./portaudio.Slackbuild

let it do it's thing, if it completes without errors it will show you where the install file is at to install it next. This done in a terminal. JICYDK (Just In Case You Don't Know)

sudo installpkg /path/package name

Simply installing portaudio won't fix this. OP will need to get all REQUIRED dependencies as well and possibly any additional optional dependencies that ponce decided to add.

It doesn't matter what the intention is. The fact is that installing things from there can lead to a broken system if you don't understand how packages work on Slackware. There is no dependency information provided, so there's no way to find out what packages you may need to get that program to work properly. Then it also displays the same package from multiple repos. Well, if one repo builds ffmpeg with h264 and another builds it without and you grab the second one, but then you grab handbrake from the first one, which expects ffmpeg to have h264 included, guess what, things are going to be broken.

This is why it is *highly* recommended to stick with one repo if you're not familiar with how this all works.

Not to mention that the owner of pkgs.org is profiting off having ponce's site listed, when s/he never reached out to ponce to see if he was ok with having his personal site linked. I have a repo available online from my home computer, but I don't want everyone to have access to it because my bandwidth would be shot. If this site owner really wants to help, he would, at a minimum, contact the people that host the sites he links to and get permission to include their repos.

As I said in my original post, you'll need to install more than just portaudio. You will need *at least* GeoIP, lua, libwacom, libinput, libxkbcommon and qt5 in addition to portaudio.

To learn how to use SlackBuilds, please see the HOWTO on the SBo site.

1. installing one deps will not break the system, if it did not work, (b)then remove everything then do it the other way. not a big loss.

he just asked about that one so I gave it to him. the list is already there to work off of.

2. I did this before just a while back, Installed the main pkg and not its dep... then figured out what I did wrong. so i went back and got the dep's installed them then it worked. no harm no foul...

...

why would you tell anyone new to do a slackpkg clean-system.
quick answer would be the prebuilt package was built against libportaudio. then tell him to install the portaudio from ponce also.
Or learn how to use slackbuilds.
clean-system wow!
To uninstall that package use the removepkg script or use pkgtool then click or select Remove tab. find the package and remove it.
But to update the system then upgrade then clean it. This is not debian. This is Slackware Linux where people come to learn linux.
How about you do to your system what you told them to do.

installing everything off of that sight for wireshark, this is for 86x_64 current slack btw
off cli after creating group adding user and setting that part of it up.
adding
missing libunistring
adding
missing libsnappy
adding
missing libicui18n
adding
returned error
ok now I am stuck at the moment.
doing this for the purpose of finding out if that sight should be red flagged? rebooting and going back in...

So, ignore the advice of forum members and just keep using it until you get burned? Sounds like a great plan. /s

BTW, I built c-ares and wireshark (the only programs I was missing) and wireshark opened fine. So, it seems to be due to the packages you have installed... possibly since they're from mixed repos.

1 members found this post helpful.

its called finding out the truth for ones self, Nothing Wrong With that!

rather that than just (always) taking someone's "word" for everything that comes out of their mouth.

what where this risk involved?

ahhh remove offending software installed which was easy enough. Nothing broke on my system I'm still on it using it.

so that "it can break my system" was bunk.

"Broken system" might've been a bit excessive, since just about anything can be fixed without wiping and reinstalling, but it can certainly cause you some hard-to-diagnose problems that could've been easily avoided (like in this example... building wireshark and the desired dependencies directly from SBo works perfectly fine... but in your case with installing packages from other repos, you need to start figuring out why qt5 doesn't recognize that xcb is available when it explicitly says underneath that xcb is available).

But that begs the question... do you have to test anything that people say is bad? It is well known that smoking cigarettes can be hazardous to your health. Many people have spoken on it and explained how it can be problematic, but do you still need to smoke and wait until you develop cancer or emphysema? It is also known that seat belts save lives, but do you need to wait until you're in an accident and get all mangled up until you decide that it might be worth using it? It is certainly your machine and you are more than welcome to use it as you desire, but there is some wisdom is learning from other's mistakes to prevent you from creating them on your own.

But then you seem to love to break your system and just reinstall things (without really trying to figure out *why* it was broke or how to properly fix it without reinstalling). I don't have the time or energy to constantly reinstall my system. It is mission-critical and when it goes down, it's not just me that's affected. So, I try to minimize the possibility of breakage in how I manage my system.

If you are totally fine with things not working as expected, feel free to keep using pkgs.net, but I've already explained how it can muck things up and if you want to ignore that, it's certainly your prerogative. Just don't assume that your willingness to experiment with your system is something that everyone wants to do. Many install Slackware for it's reputation of a stable system, so we try to encourage practices that can keep a system stable, not suggest practices that can lead to instability.