User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:22.214.171.124) Gecko/20100701 SeaMonkey/2.0.6 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:126.96.36.199) Gecko/20100701 SeaMonkey/2.0.6 Hi. I have downloaded the latest alpha version (seamonkey-2.1a2.tar.bz2), and have gotten the following error: The file jar:file:///root/seamonkey/chrome/comm.jar!/content/navigator/viewSource.xul cannot be found. Please check the location and try again. I have checked the folder to check if it was indeed there... but it is not (ie, no comm.jar! folder to be found). Kind regards, Droope Reproducible: Always Steps to Reproduce: 1. Open browser 2. Go somewhere 3. CTRL + U Actual Results: A small window will appear (like 20px x 20px ). When you expand it, you will see the error described above Expected Results: Viewing source I am using Ubuntu 8.10
How did you get to this view source? Do you have any add-ons or modifications in your version of SeaMonkey? This version of view source _and all its callers_ have been removed, you should never hit it any more!
err... I extracted the tar gz from the website, executed seamonkey.sh, and opened a website of mine. When I attempted to open the source, i got an extremely small window... when expanded, it showed the error. didn't modify the source or install plugins or anything Thank you for seamonkey ;) The best browser out there. I am now using 2.0.6
Well, as there is no tar.gz and no seamonkey.sh in our SeaMonkey 2.1 preview builds, you must have downloaded something else than our product, obviously. Still, nice to hear that you like SeaMonkey.
For record our product is from FTP at: http://releases.mozilla.org/pub/mozilla.org/seamonkey/releases/ Or you can use our project page: http://www.seamonkey-project.org/ And given that there is no .tar.gz nor a seamonkey.sh it was not a package produced by us, and we don't encounter this error, I'm resolving as invalid.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.