Closed Bug 66569 Opened 24 years ago Closed 24 years ago

unable to start linux builds

Categories

(SeaMonkey :: Build Config, defect)

x86
Linux
defect
Not set
blocker

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: bugzilla, Assigned: cls)

Details

(Keywords: platform-parity, smoketest)

i used the tarball [bad idea?], and after decompressing it then trying to run it, netscape wouldn't start up. Asa is also having startup issues with mozilla bits on linux. known issue? ftp://sweetlou.mcom.com/products/client/seamonkey/unix/linux/2.2/x86/2001-01-25-11-Mtrunk/netscape-i686-pc-linux-gnu.tar.gz output: sairuh@hopey 90: ./netscape ./run-mozilla.sh ./mozilla-bin MOZILLA_FIVE_HOME=/export/builds/2001012511/package LD_LIBRARY_PATH=/export/builds/2001012511/package:/export/builds/2001012511/package/Cool LIBPATH=/export/builds/2001012511/package:/export/builds/2001012511/package/Cool SHLIB_PATH=/export/builds/2001012511/package:/export/builds/2001012511/package/Cool XPCS_HOME=/export/builds/2001012511/package/Cool MOZ_PROGRAM=./mozilla-bin MOZ_TOOLKIT= moz_debug=0 moz_debugger= sairuh@hopey 91: i'll try out the installer bits, fwiw... btw, the sea for Mac didn't have any problems starting up... ftp://sweetlou.mcom.com/products/client/seamonkey/macos/8.x/ppc/2001-01-25-10-Mtrunk/Netscape6-mac.sea.bin
Severity: normal → blocker
Keywords: pp
hmm, perhaps this should go to installer? unsure... in any case, also fails to startup after using stubs installer. sairuh@hopey 100: ./netscape ./run-mozilla.sh ./mozilla-bin MOZILLA_FIVE_HOME=/export/builds/2001012511 LD_LIBRARY_PATH=/export/builds/2001012511:/export/builds/2001012511/Cool LIBPATH=/export/builds/2001012511:/export/builds/2001012511/Cool SHLIB_PATH=/export/builds/2001012511:/export/builds/2001012511/Cool XPCS_HOME=/export/builds/2001012511/Cool MOZ_PROGRAM=./mozilla-bin MOZ_TOOLKIT= moz_debug=0 moz_debugger= ************************************************************ * Call to xpconnect wrapped JSObject produced this error: * [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIComponentManager.registerComponentWithType]" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: /export/builds/2001012511/components/nsSidebar.js :: anonymous :: line 344" data: no] ************************************************************ ************************************************************ * Call to xpconnect wrapped JSObject produced this error: * [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIComponentManager.registerComponentWithType]" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: /export/builds/2001012511/components/nsXmlRpcClient.js :: anonymous :: line 1270" data: no] ************************************************************ ************************************************************ * Call to xpconnect wrapped JSObject produced this error: * [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIComponentManager.registerComponentWithType]" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: /export/builds/2001012511/components/nsFilePicker.js :: anonymous :: line 203" data: no] ************************************************************ ************************************************************ * Call to xpconnect wrapped JSObject produced this error: * [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIComponentManager.registerComponentWithType]" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: /export/builds/2001012511/components/nsJSAimKeywords.js :: anonymous :: line 22" data: no] ************************************************************ ************************************************************ * Call to xpconnect wrapped JSObject produced this error: * [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIComponentManager.registerComponentWithType]" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: /export/builds/2001012511/components/nsJSAimChatRendezvous.js :: anonymous :: line 44" data: no] ************************************************************ ************************************************************ * Call to xpconnect wrapped JSObject produced this error: * [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIComponentManager.registerComponentWithType]" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: /export/builds/2001012511/components/nsJSAimOdirEntry.js :: anonymous :: line 16" data: no] ************************************************************ sairuh@hopey 101:
tracy, do you see this as well?
addendum: asa saw this using today's 8am mozilla bits [not sure which download he used, though].
s/download/download type. [sheesh]
yes, I loaded the 11:00 oclock build and saw exactly that.
Keywords: smoketest
I've been seeing this ever since I've been using the tarballs (say, about a week, week and a half.) What it boils down to is that Mozilla is unable to create or manage or really even think about profiles in any way; having created a single default profile in M18, though, I can start the nightlies up without problems, and the changes I make are saved properly.
So this seems to be a profile problem? Akk's build starts up fine.
I see this problem with the 2001-01-25-11 mozilla build but I do not see it with the 2001-01-25-09 mozilla-gcc295 build. The absence or presence of an existing mozilla or netscape profile does not appear to make a difference. And I don't see this with my current tip build which is also gcc 2.95.2.
agreed. packaging issue? [my recent mozilla tip build launches fine, too.]
I've been seeing this with my cvs build for several days now.
my build from 21 o clock works fine again, while the builds after 6 o clock did not work too. fixed?
se, feel free to resolve this if this morning's bits are working for you.
dropping to critical
Severity: blocker → critical
sorry for the delay. [just came back from a brief vacation.] this is working now, using 2001.01.29.08 verification bits [mozilla on linux]. no idea what [if anything] was fixed... marking wfm.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
reopening. spoke with doron on #smoketest, who sez this might be due to earlier tree bustage [and the verification bits might've picked it up]. using 2001.01.30.08 linux mozilla tarball i now get the following: ./mozilla ./run-mozilla.sh ./mozilla-bin MOZILLA_FIVE_HOME=/home/orca/mozilla-builds/2001013008/mozilla LD_LIBRARY_PATH=/home/orca/mozilla-builds/2001013008/mozilla LIBRARY_PATH=/home/orca/mozilla-builds/2001013008/mozilla:/home/orca/mozilla-builds/2001013008/mozilla/components SHLIB_PATH=/home/orca/mozilla-builds/2001013008/mozilla LIBPATH=/home/orca/mozilla-builds/2001013008/mozilla ADDON_PATH=/home/orca/mozilla-builds/2001013008/mozilla MOZ_PROGRAM=./mozilla-bin MOZ_TOOLKIT= moz_debug=0 moz_debugger= ./mozilla-bin: error in loading shared libraries: /home/orca/mozilla-builds/2001013008/mozilla/libjsj.so: undefined symbol: JavaObject_convert if there's a respin a-comin' soon, feel free to re-resolve this... thx!
Severity: critical → blocker
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
hokay, this might likely be all platforms, if due to the bustage. feel free to file another bug for this new issue, if needed [and cc me, pls]. :)
The tree was red at the time that build was done (in a way that would cause that error if the build was done as a depend build on top of the 6am build). Setting back to WORKSFORME. According to kysmith's email, respins for Linux and Win have started and he's working on Mac.
Status: REOPENED → RESOLVED
Closed: 24 years ago24 years ago
pardon the spam: bugzilla weirdness didn't get the resolution type.
Status: RESOLVED → REOPENED
really...
Status: REOPENED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → WORKSFORME
see bug 67063 for the new problem
*zap*
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.