SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Rep:
Slackware 12.1, Seamonkey-1.1.10 (the patch)
I've upgraded Seamonkey to 1.1.10 with the patched package. Starting Seamonkey as root works as expected; however, starting Seamonkey as any user displays the window with a large gray box at the bottom (like, half an inch wide) with the "normal" bottom of window above it. Oh, yeah, there's a red "^" sitting there in the middle of the vast gray field, too.
I've upgraded Seamonkey to 1.1.10 with the patched package. Starting Seamonkey as root works as expected; however, starting Seamonkey as any user displays the window with a large gray box at the bottom (like, half an inch wide) with the "normal" bottom of window above it. Oh, yeah, there's a red "^" sitting there in the middle of the vast gray field, too.
Anybody know what's up with that?
Does Seamonkey work well with another user than root? Try creating a new user and see if it works well. If it works fine, then my guess is that somehow, the new Seamonkey is having problem either loading a config file, plugin or something else from the previous version.
In that case, try to remove (or move) your config files for seamonkey, located at your /home/<user name>. I can't say for sure which file it is, but it most likely is a hidden file (starting with a ".", ex: .seamonkey. The command "ls -a should reveal those hidden files).
Best of luck!
Last edited by Mega Man X; 07-11-2008 at 03:30 PM.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Original Poster
Rep:
It works, but there's this half-inch tall, full width gray space at the bottom of the Seamonkey window (not in root, but for every user).
BTW, there is no .seamonkey; the Seamonkey profile gets installed in .mozilla/default (and, yes, I blew that tree away, started Seamonkey, created the default profile, same thing). It's almost like some distant memory of a chrome directory or file buried somewhere or other that's not readable (but they all look like they are).
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Original Poster
Rep:
Quote:
Originally Posted by Franklin
Stupid question perhaps, but did you use the official patch from PV? If not, try that. It's working as advertised here.
Well, yeah -- and since the first missive I've uninstalled (with removepkg and reinstalled (with installpkg) and it's the same result; works properly for root, has the half-inch gray area at the bottom. I also added a new user (just to see) and had the same result. Danged annoying...
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Original Poster
Rep:
This problem appears -- appears! -- to be associated with either the SeaMonkey versions of Adblock+ or NoScript (not sure which yet) or that I didn't install them correctly when I upgraded to the patched package (who knows). Having actually read the documentation a long time ago, add-ons are supposed to be installed as root and the browser started at least once as root to "register" both add-ons and plugins; fact is, an ordinary user cannot install either Adblock+ or NoScript in SeaMonkey (even though a user can in Firefox).
Anyway, I uninstalled SeaMonkey completely, blew away /usr/lib/seamonkey* (that was left after removepkg ran), installed SeaMonkey again and, lo and behold, it works fine for root and fine for users (of course you have to screw around with renaming the "default" profile and then adding it back, but that seems to be a normal thing with SeaMonkey or Netscape back in the day).
Next step: figure out what's what with either the SeaMonkey version of Addblock+ (cripes there are a lot of ads on this site!) or NoScript.
I remember that I had this issue way back, and that it was the reason that I moved from SeaMonkey to Firefox. It was an issue with NoScript. I think you need root priviledges when you install the extension so that it gets installed on /usr/lib/seamonkey. If I remember correctly, this is because Seamonkey doesn't have the same system of extensions as Firefox does.
If this ever occurs again you can try deleting ~/.mozilla (which will delete all your options, and Firefox's too).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.