Thanks Petri!

Two packages are required to install SeaMonkey on a 64 bit x86_64 system:
seamonkey-2.9.1-x86_64-1.txz
seamonkey-solibs-2.9.1-x86_64-1.txz

And on a 32 bit x86 system:
seamonkey-2.9.1-i486-1.txz
seamonkey-solibs-2.9.1-i486-1.txz

Before I saw your post, I used the 2.10 seamonkey.Slackbuild script from the current source and the 2.9.1 source from the seamonkey-project.org and rebuilt the x86_64 packages.

http://ftp.osuosl.org/pub/slackware/...xap/seamonkey/

http://www.seamonkey-project.org/releases/2.9.1#source

Actually, if you've got the large seamonkey package, then seamonkey-solibs isn't needed. The reason the -solibs package exists is that several other packages in Slackware link to those libraries, and some users weren't happy about having to install the large package when they weren't using Seamonkey. But everything in seamonkey-solibs is already in the large seamonkey package.

BTW, if we migrate to the Mozilla nss/nspr packages (as rworkman would like to do for Xfce), then there won't be any need to have the seamonkey-solibs package as we'll be linking to that instead.

1 members found this post helpful.

FYI: Seamonkey 2.10.1 was released a couple of days ago. Use the cache_dir patch to compile the package.

Yes, I gave Seamonkey 2.10.1 a shot when I updated current, but it still has the bug.

https://bugzilla.mozilla.org/show_bug.cgi?id=736811

So I went back to 2.9.1

It appears that some versions of Firefox also have the bug, but I do not see the keyboard lock up in Firefox as badly as it does in Seamonkey.

Thanks Patrick! I was hoping you might see these postings.

Has anyone else seen this bug with Seamonkey 2.10 or 2.10.1 in current?

I'm using fvwm2.

+1 on my wishlist for that, thanks!

Seamonkey 2.11 in current now works fine.

It does not appear to have the keyboard lockup bug anymore.