Hi there!

I'm slowly getting things up to speed on my antiX 16.1 (64 bit) install going.
The inevitable bumps along the way.

I wanted to see if I could install Seamonkey, the Internet suite. Just because.
I used the Meta Package manager to install it.
But it won't show up on the menus. Tried to add it via Edit Menus in the Control Centre.
No joy there either.

I did, however, find /usr/share/install-meta/Browser-Seamonkey.bm

Does anyone know if there's another step or three I have to go through first before Seamonkey actually runs?

It's not a top priority. If it's too much trouble to install Seamonkey, I'll just stick with Firefox and Thunderbird.

Thanks in advance.

In response to your post, today I tested -- installed seamonkey via metapackageinstaller.
Immediately after installing, a seamonkey entry is immediately available in desktop menu (category:internet).
So I'm unsure"what went wrong" with your install.
Try clicking"update menu" to (again) rebuild the desktop menus & see if the new menu entries shows ups.

You could manually create a .desktop file for seamonkey if, for some reason, it's missing
Exec=/usr/bin/seamonkey
or, `apt-get purge seamonkey` and reinstall, hoping for a clean result the second time 'round.

Hi skidoo (again):

For some reason, /usr/bin/seamonkey is missing.
I'll try the purge and reinstall as you suggest.

Thanks!

NOW it works! __{{emoticon}}__

I did as you suggested: But got a message that none of it was installed.

So, I tried the Meta-Package installer again. And actually paid attention to its terminal output!
Which is when I got this error message: I think it's because the default to whether or not the user wants to install it was No, rather than Yes.

Next thing I did was And it worked just fine!

I guess I'll have to make sure not to use that use --yes option at the bottom of the Meta Package Installer screen next time.

It's getting there!

Thanks again for the nudge in the right direction!

Glad to hear you're now up-n-running. Gee, I didn't even consider that detail (the bottom checkbox in the metapackageinstaller window) and didn't realize that could have been the source of your installation grief. Yes, I had unchecked that box when testing and, no, I didn't consider mentioning that detail.

This is the nTH time I've read about that"helpful, prechecked" option causing problems. Seriously, in regard to the metapackageinstaller, I worry that the devs are trying too hard, are overcompensating in"trying to make tedious tasks magically (and mindlessly) easy".

That's fine. Got it sorted now.

And I should've noticed that error message the first time I tried the install.
Oh well, no harm done, and I learnt something new in the process!